Triple
T21880386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | León Viejo archaeological site |
E540261
|
entity |
| Predicate | distanceToNearbyModernCity |
P132960
|
FINISHED |
| Object | approximately 30 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: approximately 30 kilometers | Statement: [León Viejo archaeological site, distanceToNearbyModernCity, approximately 30 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNearbyModernCity Context triple: [León Viejo archaeological site, distanceToNearbyModernCity, approximately 30 kilometers]
-
A.
hasModernNearbyCity
chosen
Indicates that an entity is located near or in proximity to a contemporary, currently existing city.
-
B.
nearestCityTo
Indicates that one city is the closest in distance to a given location or entity compared to all other cities.
-
C.
isNearCapitalCity
Indicates that an entity is located close to, or in the immediate vicinity of, a capital city.
-
D.
containsModernCity
Indicates that one geographic or administrative region includes within its boundaries a currently existing modern city.
-
E.
nearestTownDistance
Indicates the distance from a given location to the closest town.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e600c08190bc96203f03f1e58a |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:04 p.m.