Triple
T12824307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Wards of Philadelphia |
E306608
|
entity |
| Predicate | locatedInDirectionFromCenter |
P28261
|
FINISHED |
| Object | northeast Philadelphia |
—
|
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: northeast Philadelphia | Statement: [River Wards of Philadelphia, locatedInDirectionFromCenter, northeast Philadelphia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromCenter Context triple: [River Wards of Philadelphia, locatedInDirectionFromCenter, northeast Philadelphia]
-
A.
distanceFromCentre
Indicates the measured or specified distance of an entity from a defined central point.
-
B.
distanceFromCityCenterDirection
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
C.
directionFromParkCenter
Indicates the compass direction or relative bearing of an entity when measured outward from the center point of a park.
-
D.
directionFromCityCenter
chosen
Indicates the compass direction in which one location lies relative to the city center.
-
E.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96edcc99c8190986cd78fe4714835 |
completed | April 10, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:32 p.m.