Triple
T33291017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobá |
E852317
|
entity |
| Predicate | numberOfSacbeob |
P204007
|
FINISHED |
| Object | more than 40 |
—
|
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: more than 40 | Statement: [Cobá, numberOfSacbeob, more than 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSacbeob Context triple: [Cobá, numberOfSacbeob, more than 40]
-
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.
numberOfStelae
Indicates the quantity of stelae associated with a given entity or context.
-
C.
numberOfIndividualGeoglyphsApprox
Indicates an approximate count of distinct individual geoglyphs associated with a given subject.
-
D.
numberOfArchaeologicalSites
Indicates the total count of archaeological sites associated with a given entity or context.
-
E.
longestSacbeDestination
Indicates that one location is the endpoint (destination) of the longest sacbe (ancient raised road) originating from another location.
- F. None of above. chosen
Provenance (4 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_6a0309a4e4d481908a6070b40d507aae |
completed | May 12, 2026, 11:06 a.m. |
| PD | Predicate disambiguation | batch_6a03091ac1008190bf50357364d4e9e4 |
completed | May 12, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_6a0309a3e5148190a07ab2a60529bafd |
completed | May 12, 2026, 11:06 a.m. |
Created at: May 1, 2026, 1:32 a.m.