Triple
T11564514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul–New York |
E274221
|
entity |
| Predicate | directionFromNewYork |
P100361
|
FINISHED |
| Object | westbound |
—
|
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: westbound | Statement: [Seoul–New York, directionFromNewYork, westbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromNewYork Context triple: [Seoul–New York, directionFromNewYork, westbound]
-
A.
locatedInDirectionFromNYC
Indicates that one place is situated in a specified compass direction relative to New York City.
-
B.
directionFromBoston
Indicates the compass direction or bearing of one location as measured outward from Boston.
-
C.
directionFromRochester
Indicates the compass direction or relative bearing of one place or object as measured outward starting from Rochester.
-
D.
directionFromWashingtonDC
Indicates the cardinal or relative compass direction of one place or object as measured from Washington, D.C.
-
E.
directionFromPittsburgh
Indicates the cardinal or relative compass direction in which one entity is located from Pittsburgh.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd321f88190a57ecaf079fbbc3f |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:37 p.m.