Triple
T5453335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class 222 Meridian |
E122419
|
entity |
| Predicate | hasPowerOutput |
P10373
|
FINISHED |
| Object | high power-to-weight ratio |
—
|
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 power-to-weight ratio | Statement: [Class 222 Meridian, hasPowerOutput, high power-to-weight ratio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerOutput Context triple: [Class 222 Meridian, hasPowerOutput, high power-to-weight ratio]
-
A.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
B.
designPowerOutput
chosen
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
C.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
D.
hasPowerRegulator
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
-
E.
powerplantOutput
Indicates the amount of energy or power produced by a power plant over a given period or at a specific moment.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.