Triple
T33388209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobá archaeological site |
E854976
|
entity |
| Predicate | highestStructure |
P75035
|
FINISHED |
| Object | Nohoch Mul pyramid |
—
|
NE NERFINISHED |
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: Nohoch Mul pyramid | Statement: [Cobá archaeological site, highestStructure, Nohoch Mul pyramid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestStructure Context triple: [Cobá archaeological site, highestStructure, Nohoch Mul pyramid]
-
A.
hasHighestStructure
chosen
Indicates that an entity possesses the tallest or most elevated structural feature compared to all other relevant entities in a given context.
-
B.
highestOrgan
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
-
C.
topStructure
Indicates that one structure occupies the highest or most superior position relative to other structures within a given system or hierarchy.
-
D.
highestPart
Indicates that one entity is the topmost or uppermost portion of another entity.
-
E.
highestDecorationOf
Indicates that one decoration or honor is the most prestigious or highest-ranking award received by a given entity.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:35 a.m.