Triple
T25629603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 5D-33 |
E642534
|
entity |
| Predicate | isBuiltBy |
P13567
|
FINISHED |
| Object | Maya builders of Tikal |
—
|
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: Maya builders of Tikal | Statement: [Temple 5D-33, isBuiltBy, Maya builders of Tikal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBuiltBy Context triple: [Temple 5D-33, isBuiltBy, Maya builders of Tikal]
-
A.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
B.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
C.
originallyBuiltBy
chosen
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
D.
builtByOfficial
Indicates that something was constructed or created by an official or authorized person or body.
-
E.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
- 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_69f5fa260734819080d7d32c6912d267 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:17 p.m.