Triple
T1161070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run 3 (2022– ) |
E24490
|
entity |
| Predicate | energyHigherThan |
P25628
|
FINISHED |
| Object | Run 2 (2015–2018) |
—
|
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: Run 2 (2015–2018) | Statement: [Run 3 (2022– ), energyHigherThan, Run 2 (2015–2018)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyHigherThan Context triple: [Run 3 (2022– ), energyHigherThan, Run 2 (2015–2018)]
-
A.
isHigherThan
Indicates that one entity has a greater value, level, or position than another entity.
-
B.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
C.
higherValueIndicates
Indicates that a greater numerical or qualitative value of one entity corresponds to a stronger presence, importance, or intensity of a specified property or outcome relative to another.
-
D.
higherDenomination
Indicates that one entity represents a monetary value that is greater than the monetary value represented by another entity.
-
E.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
- F. None of above. chosen
Provenance (4 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb1915081908834ced85d09e299 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:45 p.m.