Triple
T27225188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Chain across the Hudson River |
E681390
|
entity |
| Predicate | stretchedBetween |
P122441
|
FINISHED |
| Object | Constitution Island |
—
|
NE NERFINISHED |
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: Constitution Island | Statement: [Great Chain across the Hudson River, stretchedBetween, Constitution Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stretchedBetween Context triple: [Great Chain across the Hudson River, stretchedBetween, Constitution Island]
-
A.
stretchedFrom
chosen
Indicates that one entity extends or reaches out in space or time starting at another specified entity or point.
-
B.
isStretchOf
Indicates that one linear feature (such as a road, river, or path) constitutes a continuous segment or portion of another, longer linear feature.
-
C.
gapBetween
Indicates the spatial or temporal distance or separation that exists between two entities.
-
D.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
E.
hasLongStretchIn
Indicates that something extends for a considerable or continuous distance within a specified area, medium, or context.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6264a03648190a9b6904ce2f7aeeb |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 9:44 a.m.