Triple
T37188750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marion Bridge |
E921390
|
entity |
| Predicate | isInWaterBasin |
P18951
|
FINISHED |
| Object | Mira River watershed |
—
|
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: Mira River watershed | Statement: [Marion Bridge, isInWaterBasin, Mira River watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInWaterBasin Context triple: [Marion Bridge, isInWaterBasin, Mira River watershed]
-
A.
hasPositionInWatercourse
Indicates that one entity occupies a specific location or position within the course of a body of water.
-
B.
hasWaterBasins
Indicates that one entity possesses, contains, or includes one or more water basins in relation to another entity.
-
C.
isInlandWaterBody
Indicates that one entity is a body of water located inland (such as a lake, river, or reservoir) rather than part of the open ocean or sea.
-
D.
isLocatedNearBasin
Indicates that one entity is situated close to or in the immediate vicinity of a basin.
-
E.
locatedInBasin
chosen
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.