Triple
T24387438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity Bridge |
E614785
|
entity |
| Predicate | riverStatus |
P116775
|
FINISHED |
| Object | rivers now diverted or vanished |
—
|
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: rivers now diverted or vanished | Statement: [Trinity Bridge, riverStatus, rivers now diverted or vanished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverStatus Context triple: [Trinity Bridge, riverStatus, rivers now diverted or vanished]
-
A.
riverStatusAtLocation
chosen
Indicates the condition or state of a river at a specific geographic location.
-
B.
waterwayStatus
Indicates the current navigational or operational condition of a waterway, such as whether it is open, restricted, or closed for use.
-
C.
currentHydrology
Indicates the present state or characteristics of water flow, distribution, and related hydrological conditions associated with an entity.
-
D.
riverPhenomenon
Indicates a natural event, condition, or process that occurs in or directly affects a river.
-
E.
hasRiverActivity
Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29455e7fc8190841f909b970f6bd3 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.