Triple
T36075710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERS |
E1043489
|
entity |
| Predicate | hasPowerOutputLimit |
P194754
|
FINISHED |
| Object | 120 kW (approximate, FIA-regulated) |
—
|
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: 120 kW (approximate, FIA-regulated) | Statement: [ERS, hasPowerOutputLimit, 120 kW (approximate, FIA-regulated)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerOutputLimit Context triple: [ERS, hasPowerOutputLimit, 120 kW (approximate, FIA-regulated)]
-
A.
hasPowerCapacity
chosen
Indicates that an entity possesses a specified amount or limit of power it can produce, handle, or store.
-
B.
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.
-
C.
optionalPowerOutput
Indicates that an entity may have a specified power output value, but this value is not required to be present.
-
D.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
E.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 3, 2026, 4:08 p.m.