Triple
T4065758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMRTG |
E86318
|
entity |
| Predicate | electricalPowerAtBeginningOfLife |
P30474
|
FINISHED |
| Object | approximately 110 watts |
—
|
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: approximately 110 watts | Statement: [MMRTG, electricalPowerAtBeginningOfLife, approximately 110 watts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricalPowerAtBeginningOfLife Context triple: [MMRTG, electricalPowerAtBeginningOfLife, approximately 110 watts]
-
A.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
B.
intendedPower
chosen
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
-
C.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
D.
inPowerSince
Indicates the point in time from which an entity has continuously held a position of authority or power.
-
E.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.