Triple
T25778650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Structure 44 |
E649223
|
entity |
| Predicate | hasInscriptionsAbout |
P16756
|
FINISHED |
| Object | rulers 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: rulers of Yaxchilán | Statement: [Structure 44, hasInscriptionsAbout, rulers of Yaxchilán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInscriptionsAbout Context triple: [Structure 44, hasInscriptionsAbout, rulers of Yaxchilán]
-
A.
hasInscriptions
chosen
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
B.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
C.
hasTypeOfInscriptions
Indicates that an entity bears or is associated with a specific kind or category of inscriptions.
-
D.
mayBeInscribedOn
Indicates that one entity is permitted or suitable to be written, engraved, or otherwise inscribed on another entity.
-
E.
issuedInscriptionsIn
Indicates that an entity (such as an authority or issuer) produced or authorized inscriptions within a specified place or context.
- 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_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 22, 2026, 5:36 a.m.