Triple
T33660540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rankine cycle |
E862337
|
entity |
| Predicate | analyzedOn |
P159600
|
FINISHED |
| Object | temperature-entropy diagram |
—
|
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: temperature-entropy diagram | Statement: [Rankine cycle, analyzedOn, temperature-entropy diagram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analyzedOn Context triple: [Rankine cycle, analyzedOn, temperature-entropy diagram]
-
A.
conductedOn
chosen
Indicates that an action, process, or event was carried out with respect to, or took place on, a specified subject, object, or medium.
-
B.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
C.
oftenAnalyzedIn
Indicates that something is frequently examined, studied, or evaluated within a particular context, field, or framework.
-
D.
timePeriodAnalyzed
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
-
E.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
- 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_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:42 a.m.