Triple
T22756584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peugeot 9X8 |
E562858
|
entity |
| Predicate | maximumCombinedPower |
P102364
|
FINISHED |
| Object | 500 kW (regulated by LMH rules) |
—
|
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: 500 kW (regulated by LMH rules) | Statement: [Peugeot 9X8, maximumCombinedPower, 500 kW (regulated by LMH rules)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCombinedPower Context triple: [Peugeot 9X8, maximumCombinedPower, 500 kW (regulated by LMH rules)]
-
A.
combinesPowers
chosen
Indicates that two or more entities merge their abilities or strengths to produce a unified, often enhanced, effect.
-
B.
maximumPowerDuringOperation
Indicates the highest level of power that occurs while the system or component is operating.
-
C.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
D.
maximumEnergy
Indicates the greatest amount of energy that an entity can possess, store, or output under specified conditions.
-
E.
laterPowerOutput
Indicates that the power output of an entity at a later time is being related or compared to its power output at an earlier time.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bd22588190ac724a656194f5b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.