Triple
T33290815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobá road network |
E852313
|
entity |
| Predicate | Sacbe 1 |
P93072
|
FINISHED |
| Object | connects Cobá to Yaxuná |
—
|
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: connects Cobá to Yaxuná | Statement: [Cobá road network, Sacbe 1, connects Cobá to Yaxuná]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Sacbe 1 Context triple: [Cobá road network, Sacbe 1, connects Cobá to Yaxuná]
-
A.
hasSacbe
Indicates a relationship where one place or structure possesses, is connected by, or is associated with a sacbe (an ancient raised road or causeway).
-
B.
SakaeIs
Indicates that one entity is identified as or classified as "Sakae" in relation to another entity or context.
-
C.
סב
Indicates a familial relationship where one entity is the grandfather of another.
-
D.
قبلة
Indicates a kissing action or gesture occurring between entities.
-
E.
connectedBySacbeTo
chosen
Indicates that one entity is linked or joined to another by a sacbe, an ancient raised road or causeway.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:32 a.m.