Triple
T25629520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple II |
E642532
|
entity |
| Predicate | belongsToSiteType |
P53032
|
FINISHED |
| Object | ancient Maya city |
—
|
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: ancient Maya city | Statement: [Temple II, belongsToSiteType, ancient Maya city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSiteType Context triple: [Temple II, belongsToSiteType, ancient Maya city]
-
A.
associatedSiteType
chosen
Indicates the type or category of site with which an entity is associated.
-
B.
belongsToSystemType
Indicates that one entity is classified under, or is a member of, a particular system type.
-
C.
hasTypeSiteFor
Indicates that one entity serves as the specific site or location designated for a particular type or category of another entity.
-
D.
hasComponentSiteType
Indicates that an entity includes or is associated with a component whose location or role is classified by a specific site type.
-
E.
belongsToDocumentType
Indicates that one entity is classified under, or associated with, a specific document type.
- 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_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 5:17 p.m.