Triple
T33388215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobá archaeological site |
E854976
|
entity |
| Predicate | sacbeobTotalLength |
P54232
|
FINISHED |
| Object | over 100 kilometers |
—
|
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: over 100 kilometers | Statement: [Cobá archaeological site, sacbeobTotalLength, over 100 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacbeobTotalLength Context triple: [Cobá archaeological site, sacbeobTotalLength, over 100 kilometers]
-
A.
totalLength_m
Indicates the overall measured length of something expressed in meters.
-
B.
commonTotalLength
Indicates that the entities share the same overall measured length.
-
C.
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).
-
D.
longestSacbeDestination
Indicates that one location is the endpoint (destination) of the longest sacbe (ancient raised road) originating from another location.
-
E.
totalSystemLength
chosen
Indicates the complete measured length of an entire system, aggregating all its relevant components or segments.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:35 a.m.