Triple
T23519496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mausoleum of the First Qin Emperor |
E574462
|
entity |
| Predicate | discoveryOfTerracottaArmy |
P132164
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Mausoleum of the First Qin Emperor, discoveryOfTerracottaArmy, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfTerracottaArmy Context triple: [Mausoleum of the First Qin Emperor, discoveryOfTerracottaArmy, 1974]
-
A.
tombDiscovered
Indicates that a tomb has been found or uncovered, typically as the result of exploration, excavation, or chance discovery.
-
B.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
C.
excavatedBy
Indicates that something (typically an archaeological site, artifact, or geological feature) was uncovered or dug out by a particular agent (such as a person, team, or organization).
-
D.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
E.
relicsDiscoveryYear
chosen
Indicates the year in which the relics were discovered.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa84fe7c8190aa1078a118af7d61 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f06213e8c48190b52a7789fb91e02d |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.