Triple
T20251848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Reaches |
E498574
|
entity |
| Predicate | waterwayCondition |
P19096
|
FINISHED |
| Object | partly unnavigable |
—
|
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: partly unnavigable | Statement: [Northern Reaches, waterwayCondition, partly unnavigable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayCondition Context triple: [Northern Reaches, waterwayCondition, partly unnavigable]
-
A.
waterwayStatus
chosen
Indicates the current navigational or operational condition of a waterway, such as whether it is open, restricted, or closed for use.
-
B.
riverStatusAtLocation
Indicates the condition or state of a river at a specific geographic location.
-
C.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
D.
stateWaterway
Indicates that a waterway is located within, passes through, or is otherwise geographically associated with a particular state.
-
E.
waterwayContext
Indicates that one entity is a waterway whose characteristics, usage, or significance are defined or influenced by its surrounding geographic or environmental context.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a8b8488190b344df7a65f59684 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.