Triple
T27644566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tottenville Ferry Slip |
E696674
|
entity |
| Predicate | crossedWaterbody |
P15424
|
FINISHED |
| Object | Arthur Kill |
—
|
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: Arthur Kill | Statement: [Tottenville Ferry Slip, crossedWaterbody, Arthur Kill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossedWaterbody Context triple: [Tottenville Ferry Slip, crossedWaterbody, Arthur Kill]
-
A.
crossesWaterBody
chosen
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
B.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
C.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
D.
crossesWatershed
Indicates that one entity passes from one drainage basin or watershed area into another, traversing the boundary between them.
-
E.
lakeTypeCrossed
Indicates that one entity has traversed or passed across a lake of a specified type.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 2:28 p.m.