Triple
T28373411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 法门寺 |
E718692
|
entity |
| Predicate | discoveredRelics |
P87690
|
FINISHED |
| Object | 1987年地宫发掘佛指舍利 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1987年地宫发掘佛指舍利 | Statement: [法门寺, discoveredRelics, 1987年地宫发掘佛指舍利]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredRelics Context triple: [法门寺, discoveredRelics, 1987年地宫发掘佛指舍利]
-
A.
relicDiscovery
chosen
Indicates the event or relationship in which an entity finds or uncovers a relic.
-
B.
relicsDiscoveryYear
Indicates the year in which the relics were discovered.
-
C.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
-
D.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
-
E.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 1:01 a.m.