Triple
T21310084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assunpink Creek |
E525305
|
entity |
| Predicate | hasWaterbodyOnCourse |
P56309
|
FINISHED |
| Object | Assunpink Lake |
—
|
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: Assunpink Lake | Statement: [Assunpink Creek, hasWaterbodyOnCourse, Assunpink Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterbodyOnCourse Context triple: [Assunpink Creek, hasWaterbodyOnCourse, Assunpink Lake]
-
A.
waterbodyOnCourse
chosen
Indicates that a waterbody lies along, intersects, or is situated on the path of a particular course, such as a river or stream.
-
B.
navigatesWaterBody
Indicates that an entity moves through or across a body of water as a means of travel or operation.
-
C.
hasWaterBodyOnWest
Indicates that a specified entity has a water body located to its west.
-
D.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
E.
involvesBodyOfWater
Indicates that the relationship or event includes, affects, or takes place in connection with a body of water such as a sea, lake, river, or ocean.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aaa56fc81909ba7649302528269 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:06 p.m.