Triple
T5750222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youghiogheny River |
E126832
|
entity |
| Predicate | hasRapidsClass |
P66518
|
FINISHED |
| Object | Class III |
—
|
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: Class III | Statement: [Youghiogheny River, hasRapidsClass, Class III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRapidsClass Context triple: [Youghiogheny River, hasRapidsClass, Class III]
-
A.
hasRapids
Indicates that a body of water contains sections of fast-flowing, turbulent water known as rapids.
-
B.
hasFeatureClass
Indicates that an entity is associated with, or categorized under, a particular feature class that characterizes its type or nature.
-
C.
hasCoreClass
Indicates that an entity is associated with, or belongs to, a primary or fundamental class within a classification system.
-
D.
hasIceClass
Indicates that an object (typically a vessel or structure) is assigned a specific ice classification denoting its capability to operate in icy or ice-infested waters.
-
E.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
- F. None of above. chosen
Provenance (4 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b4ea03c81908c3d799462de20c4 |
completed | March 22, 2026, 5:47 p.m. |
Created at: March 22, 2026, 3:48 p.m.