Triple
T14978956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaplan turbine |
E373525
|
entity |
| Predicate | suitableFlowCondition |
P68538
|
FINISHED |
| Object | large discharge |
—
|
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: large discharge | Statement: [Kaplan turbine, suitableFlowCondition, large discharge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitableFlowCondition Context triple: [Kaplan turbine, suitableFlowCondition, large discharge]
-
A.
flowCondition
chosen
Indicates the condition or set of criteria under which a flow, process, or transition is allowed to occur.
-
B.
supportsCondition
Indicates that one entity helps maintain, enable, or is compatible with a particular condition or state in another entity.
-
C.
regulatesFlowBetween
Indicates a relationship where one entity controls, directs, or modulates the movement or transfer of something (such as material, energy, or information) between two other entities.
-
D.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
E.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
- 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.