Triple
T13437670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Inland Voyage |
E320270
|
entity |
| Predicate | describesWaterwayType |
P27890
|
FINISHED |
| Object | river |
—
|
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: river | Statement: [An Inland Voyage, describesWaterwayType, river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesWaterwayType Context triple: [An Inland Voyage, describesWaterwayType, river]
-
A.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
B.
isWaterway
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
-
C.
hasWatercourseType
chosen
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
D.
stateWaterway
Indicates that a waterway is located within, passes through, or is otherwise geographically associated with a particular state.
-
E.
waterwayFunction
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee42a8c8190a85716b4a6db335e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.