Triple
T25778629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Structure 33 |
E649222
|
entity |
| Predicate | belongsToSiteCore |
P131774
|
FINISHED |
| Object | central monumental group of Yaxchilán |
—
|
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: central monumental group of Yaxchilán | Statement: [Structure 33, belongsToSiteCore, central monumental group of Yaxchilán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSiteCore Context triple: [Structure 33, belongsToSiteCore, central monumental group of Yaxchilán]
-
A.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
B.
belongsToModule
Indicates that something is a component or part of a specific module within a larger system or structure.
-
C.
associatedSiteType
Indicates the type or category of site with which an entity is associated.
-
D.
hasSiteContext
chosen
Indicates that something is associated with, occurs within, or is interpreted relative to a particular site or contextual environment.
-
E.
belongsToPlatform
Indicates that something is associated with, owned by, or part of a particular 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 22, 2026, 5:36 a.m.