Triple
T2237280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calakmul |
E49310
|
entity |
| Predicate | hasUrbanAreaApprox |
P37282
|
FINISHED |
| Object | over 2 square kilometres |
—
|
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 2 square kilometres | Statement: [Calakmul, hasUrbanAreaApprox, over 2 square kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanAreaApprox Context triple: [Calakmul, hasUrbanAreaApprox, over 2 square kilometres]
-
A.
containsUrbanArea
Indicates that a geographic region fully or partially encompasses an urbanized area within its boundaries.
-
B.
withinUrbanArea
Indicates that one entity is located inside the spatial boundaries of an urban area associated with another entity.
-
C.
isUrbanized
Indicates that a place or area has been developed with dense human settlement, infrastructure, and built environment characteristic of a city or town.
-
D.
hasUrbanFunction
Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
-
E.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09573848190bf91eddcc2fa0061 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:47 p.m.