Triple
T33660519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rankine cycle |
E862337
|
entity |
| Predicate | hasState1 |
P197262
|
FINISHED |
| Object | high-pressure liquid water at pump outlet |
—
|
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: high-pressure liquid water at pump outlet | Statement: [Rankine cycle, hasState1, high-pressure liquid water at pump outlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasState1 Context triple: [Rankine cycle, hasState1, high-pressure liquid water at pump outlet]
-
A.
hasStateOf
chosen
Indicates that an entity possesses, exhibits, or is currently in a particular condition, status, or mode.
-
B.
hadStateFrom
Indicates that an entity possessed or was in a particular state starting from a specified point in time.
-
C.
hasStateSystem
Indicates that an entity possesses, follows, or is governed by a particular system of state organization, rules, or governance.
-
D.
hasSubjectState
Indicates that an entity (typically an event, statement, or situation) is associated with a particular state or condition of its subject.
-
E.
hasStateMuffin
Indicates that an entity is in a particular "muffin" state or condition, typically representing a specific status labeled as "muffin."
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: May 1, 2026, 1:42 a.m.