Triple
T34530509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metra fare zone H |
E886523
|
entity |
| Predicate | relativeDistanceFrom |
P120034
|
FINISHED |
| Object | downtown Chicago |
E164916
|
NE 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: downtown Chicago | Statement: [Metra fare zone H, relativeDistanceFrom, downtown Chicago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeDistanceFrom Context triple: [Metra fare zone H, relativeDistanceFrom, downtown Chicago]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
approximateDistanceFrom
Indicates an estimated or rough measure of how far one entity is from another.
-
D.
distancesFrom
chosen
Indicates the measured spatial separation between one entity and one or more other entities.
-
E.
isFurtherFrom
Indicates that one entity is at a greater distance from a reference point or object than another entity is.
- F. None of above.
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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37361bbeac8190889accab4cf0b6f7 |
completed | June 21, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.