Triple
T35561847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impero |
E1027654
|
entity |
| Predicate | designedPowerOutput |
P10373
|
FINISHED |
| Object | about 128000 shp |
—
|
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: about 128000 shp | Statement: [Impero, designedPowerOutput, about 128000 shp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedPowerOutput Context triple: [Impero, designedPowerOutput, about 128000 shp]
-
A.
designPowerOutput
chosen
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
B.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
C.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
-
D.
optionalPowerOutput
Indicates that an entity may have a specified power output value, but this value is not required to be present.
-
E.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity or system.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 3, 2026, 4:04 p.m.