Triple
T20289405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenkins Township |
E509977
|
entity |
| Predicate | locatedInDirectionFromWilkes-Barre |
P139551
|
FINISHED |
| Object | northeast Pennsylvania |
—
|
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 Pennsylvania | Statement: [Jenkins Township, locatedInDirectionFromWilkes-Barre, northeast Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromWilkes-Barre Context triple: [Jenkins Township, locatedInDirectionFromWilkes-Barre, northeast Pennsylvania]
-
A.
directionFromPittsburgh
Indicates the cardinal or relative compass direction in which one entity is located from Pittsburgh.
-
B.
locatedInDirectionFromNYC
Indicates that one place is situated in a specified compass direction relative to New York City.
-
C.
distanceToPennsylvaniaBorder
Indicates the measured distance between a given location and the border of Pennsylvania.
-
D.
directionFromTrenton
Indicates the cardinal or relative compass direction in which one entity is located from Trenton.
-
E.
distanceToScranton
Indicates the spatial distance between a given entity and the location Scranton.
- F. None of above. chosen
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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67694d50881909d59c1037295c1d0 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:11 a.m.