Triple
T18727849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York–London |
E457952
|
entity |
| Predicate | directionWestbound |
P24810
|
FINISHED |
| Object | London to New York |
—
|
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: London to New York | Statement: [New York–London, directionWestbound, London to New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionWestbound Context triple: [New York–London, directionWestbound, London to New York]
-
A.
directionEastSide
Indicates that one entity is located on or oriented toward the eastern side of another entity.
-
B.
transportDirection
chosen
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
C.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
D.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
E.
boundedToWestBy
Indicates that one entity’s western boundary is defined or delimited by another entity.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d74bd9881908cd314e68327c402 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:50 a.m.