Triple
T38339104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguar XK140 |
E1038042
|
entity |
| Predicate | standardPowerOutput |
P89369
|
FINISHED |
| Object | 190 bhp |
—
|
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: 190 bhp | Statement: [Jaguar XK140, standardPowerOutput, 190 bhp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardPowerOutput Context triple: [Jaguar XK140, standardPowerOutput, 190 bhp]
-
A.
optionalPowerOutput
Indicates that an entity may have a specified power output value, but this value is not required to be present.
-
B.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
C.
powerOutputType
Indicates the specific form or category of power output associated with an entity, such as electrical, mechanical, or thermal.
-
D.
typicalPower
chosen
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
-
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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:30 p.m.