Triple
T25629512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple II |
E642532
|
entity |
| Predicate | isMajorMonumentOf |
P145972
|
FINISHED |
| Object | Tikal |
—
|
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: Tikal | Statement: [Temple II, isMajorMonumentOf, Tikal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorMonumentOf Context triple: [Temple II, isMajorMonumentOf, Tikal]
-
A.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
B.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
C.
monumentSubject
Indicates that the subject serves as the monument or commemorative structure associated with another entity.
-
D.
hasPrimaryMonument
chosen
Indicates that an entity is associated with its main or most significant monument.
-
E.
otherMonuments
Indicates that there exists a relationship between an entity and additional monuments that are associated with or related to it in some relevant way.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 5:17 p.m.