Triple
T4635975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverhead |
E101532
|
entity |
| Predicate | geographicDirectionOnLongIsland |
P57874
|
FINISHED |
| Object | eastern end |
—
|
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: eastern end | Statement: [Riverhead, geographicDirectionOnLongIsland, eastern end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicDirectionOnLongIsland Context triple: [Riverhead, geographicDirectionOnLongIsland, eastern end]
-
A.
geographicDirectionWithinCountry
Indicates that one place lies in a specified cardinal or intercardinal direction relative to another place within the same country.
-
B.
geographicDirectionWithinState
Indicates that one location lies in a specified cardinal or relative geographic direction within the boundaries of a particular state.
-
C.
directionFromEarth
Indicates the compass or spatial direction in which an entity is located as observed from Earth.
-
D.
directionFromBoston
Indicates the compass direction or bearing of one location as measured outward from Boston.
-
E.
hasStreetDirection
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a60a66c8190b76f3d3a7da1df55 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56f7b94481909f3335312becd446 |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:13 p.m.