Triple
T2413356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templo Mayor |
E52244
|
entity |
| Predicate | discoveryEvent |
P37746
|
FINISHED |
| Object | 1978 discovery of Coyolxauhqui stone |
—
|
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: 1978 discovery of Coyolxauhqui stone | Statement: [Templo Mayor, discoveryEvent, 1978 discovery of Coyolxauhqui stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryEvent Context triple: [Templo Mayor, discoveryEvent, 1978 discovery of Coyolxauhqui stone]
-
A.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
B.
reportsDiscoveryOf
Indicates that one entity formally announces or documents the finding or uncovering of another entity (typically a new object, fact, or phenomenon).
-
C.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
D.
discoveredWith
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
- F. None of above. chosen
Provenance (4 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc94a6458819087b8c4fe81a2d031 |
completed | March 7, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6011e348190b6f9c038c7559289 |
completed | March 7, 2026, 6:30 a.m. |
Created at: March 6, 2026, 9:41 p.m.