Triple
T10246994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eje 1 Norte |
E240240
|
entity |
| Predicate | positionRelativeToCenter |
P23578
|
FINISHED |
| Object | north of Mexico City historic center |
—
|
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: north of Mexico City historic center | Statement: [Eje 1 Norte, positionRelativeToCenter, north of Mexico City historic center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToCenter Context triple: [Eje 1 Norte, positionRelativeToCenter, north of Mexico City historic center]
-
A.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
B.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
positionRelativeToBuilding
Indicates the spatial relationship of an entity’s location with respect to a specific building (e.g., in front of, behind, adjacent to, on top of).
-
D.
movementCenter
Indicates the central point or primary location around which an entity’s movement or motion is organized or focused.
-
E.
positionRelativeToTower
Indicates the spatial relationship or placement of an entity with respect to a specified tower.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:27 a.m.