Triple
T2444411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beer Kill |
E53355
|
entity |
| Predicate | watercourseCategory |
P27890
|
FINISHED |
| Object | small stream |
—
|
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: small stream | Statement: [Beer Kill, watercourseCategory, small stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseCategory Context triple: [Beer Kill, watercourseCategory, small stream]
-
A.
watercourseName
Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
-
B.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
C.
hasWatercourseType
chosen
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
D.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
E.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.