Triple
T33291036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobá |
E852317
|
entity |
| Predicate | sacbeobDefinition |
P37689
|
FINISHED |
| Object | raised stone causeways |
—
|
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: raised stone causeways | Statement: [Cobá, sacbeobDefinition, raised stone causeways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacbeobDefinition Context triple: [Cobá, sacbeobDefinition, raised stone causeways]
-
A.
hasSacbe
chosen
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.
connectedBySacbeTo
Indicates that one entity is linked or joined to another by a sacbe, an ancient raised road or causeway.
-
C.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
SakaeIs
Indicates that one entity is identified as or classified as "Sakae" in relation to another entity or context.
-
E.
sacredDirection
Indicates a directional relationship that is regarded as holy, spiritually significant, or ritually privileged within a religious or cultural 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:32 a.m.