Triple
T7195920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaxchilán |
E168613
|
entity |
| Predicate | hasModernAccess |
P37747
|
FINISHED |
| Object | boat on Usumacinta River |
—
|
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: boat on Usumacinta River | Statement: [Yaxchilán, hasModernAccess, boat on Usumacinta River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernAccess Context triple: [Yaxchilán, hasModernAccess, boat on Usumacinta River]
-
A.
hasModernLocation
Indicates that an entity is currently situated in, or corresponds to, a specified modern geographic or administrative location.
-
B.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
C.
hasModernMaterial
Indicates that an entity incorporates or is made from contemporary, recently developed, or non-traditional materials.
-
D.
modernAccess
chosen
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
E.
hasModernSquare
Indicates that an entity possesses or includes a square-shaped feature designed or styled in a modern 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e927709c81909edf6ee42fe7f833 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:51 p.m.