Triple
T7025085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defiant Mk I |
E162922
|
entity |
| Predicate | powerplantHorsepowerClass |
P5894
|
FINISHED |
| Object | about 1,000 hp |
—
|
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 1,000 hp | Statement: [Defiant Mk I, powerplantHorsepowerClass, about 1,000 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplantHorsepowerClass Context triple: [Defiant Mk I, powerplantHorsepowerClass, about 1,000 hp]
-
A.
powerplantThrustClass
Indicates the classification of a powerplant based on the level or range of thrust it produces.
-
B.
powerClassBR
Indicates a relationship where one entity is classified or grouped according to its power-related category or level relative to another entity.
-
C.
horsepower
chosen
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
D.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
E.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.