Triple
T24777713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rancocas Valley |
E619906
|
entity |
| Predicate | flowsIntoViaRancocasCreek |
P91112
|
FINISHED |
| Object | Delaware River |
—
|
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: Delaware River | Statement: [Rancocas Valley, flowsIntoViaRancocasCreek, Delaware River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsIntoViaRancocasCreek Context triple: [Rancocas Valley, flowsIntoViaRancocasCreek, Delaware River]
-
A.
flowsIntoBodyOfWaterAt
Indicates that one body of water moves or drains into another body of water at a specific location or point.
-
B.
flowsIntoBodyOfWaterType
Indicates that one body of water moves or drains into another body of water of a specified type (e.g., river, lake, ocean).
-
C.
flowsIntoViaMainRiver
chosen
Indicates that one water body ultimately flows into another through the course of a primary or main river channel.
-
D.
flowsIntoBodyOfWaterNear
Indicates that one body of water flows into another body of water at or near a specific location.
-
E.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410d3ea308190ae80cb7d5bf94249 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:41 a.m.