Triple
T14978954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaplan turbine |
E373525
|
entity |
| Predicate | suitableHeadRange |
P49736
|
FINISHED |
| Object | low head |
—
|
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: low head | Statement: [Kaplan turbine, suitableHeadRange, low head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitableHeadRange Context triple: [Kaplan turbine, suitableHeadRange, low head]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
C.
hostRange
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
-
D.
designedRange
chosen
Indicates the intended or specified range within which something is designed to operate or be effective.
-
E.
hasHeadCount
Indicates that an entity is associated with a specific number of individuals, typically representing the size or count of people (or similar units) related to it.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6fcebf481909f72cab577560d82 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:51 a.m.