Triple
T7401472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Line, Philadelphia |
E170758
|
entity |
| Predicate | directionFromPhiladelphiaCenterCity |
P28261
|
FINISHED |
| Object | northwest |
—
|
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: northwest | Statement: [Main Line, Philadelphia, directionFromPhiladelphiaCenterCity, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromPhiladelphiaCenterCity Context triple: [Main Line, Philadelphia, directionFromPhiladelphiaCenterCity, northwest]
-
A.
directionFromPittsburgh
Indicates the cardinal or relative compass direction in which one entity is located from Pittsburgh.
-
B.
distanceFromCityCenterDirection
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
C.
directionFromCityCenter
chosen
Indicates the compass direction in which one location lies relative to the city center.
-
D.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
-
E.
directionFromTrenton
Indicates the cardinal or relative compass direction in which one entity is located from Trenton.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24f6b7c81908cb61395239d03a0 |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.