Triple
T31808898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tongonan Geothermal Field |
E811948
|
entity |
| Predicate | conversionTechnology |
P176751
|
FINISHED |
| Object | steam turbines |
—
|
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: steam turbines | Statement: [Tongonan Geothermal Field, conversionTechnology, steam turbines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionTechnology Context triple: [Tongonan Geothermal Field, conversionTechnology, steam turbines]
-
A.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
B.
conversionWave
Indicates a process in which changes or transformations spread through entities or states in a sequential, wave-like manner.
-
C.
conversionTarget
Indicates that one entity serves as the intended outcome, goal, or result that another entity is meant to be converted or transformed into.
-
D.
conversionProgram
Indicates a program or process that transforms something from one form, state, or type into another.
-
E.
conversionMode
chosen
Indicates the specific method or setting by which one form, unit, or representation is transformed into another.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 30, 2026, 11:43 p.m.