Triple
T25272277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Liverpool, New York |
E633597
|
entity |
| Predicate | directionFromSyracuse |
P162999
|
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: [Village of Liverpool, New York, directionFromSyracuse, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromSyracuse Context triple: [Village of Liverpool, New York, directionFromSyracuse, northwest]
-
A.
directionFromRochester
Indicates the compass direction or relative bearing of one place or object as measured outward starting from Rochester.
-
B.
directionFromNewYork
Indicates the cardinal or relative compass direction of an entity or location as measured from New York.
-
C.
directionFromColumbus
Indicates the compass direction in which one location lies when measured from Columbus.
-
D.
distanceToSyracuse
Indicates the spatial distance between a given entity’s location and the location of Syracuse.
-
E.
locatedInDirectionFromNYC
Indicates that one place is situated in a specified compass direction relative to New York City.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 21, 2026, 1:16 p.m.