Triple
T34692939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East-of-Hudson service |
E890947
|
entity |
| Predicate | hasDirectionRelativeToHudsonRiver |
P199074
|
FINISHED |
| Object | east |
—
|
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: east | Statement: [East-of-Hudson service, hasDirectionRelativeToHudsonRiver, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionRelativeToHudsonRiver Context triple: [East-of-Hudson service, hasDirectionRelativeToHudsonRiver, east]
-
A.
distanceToHudsonRiver
Indicates the measured or specified distance between a given entity’s location and the Hudson River.
-
B.
hasBoroughAcrossHudson
Indicates that one entity has a borough or administrative subdivision located on the opposite side of the Hudson River from another referenced entity.
-
C.
isHistoricHudsonRiverCommunity
Indicates that a community is historically recognized as part of the Hudson River region, often due to its cultural, architectural, or historical significance tied to the river.
-
D.
rankAtPortHudson
Indicates the military rank a person held specifically during the engagement at Port Hudson.
-
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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
| PDg | Predicate description generation | batch_69ff1d8394988190acf163a07acad200 |
completed | May 9, 2026, 11:41 a.m. |
Created at: May 1, 2026, 2:05 a.m.