Triple
T18692024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waco UPF-7 |
E457022
|
entity |
| Predicate | enginePowerClass |
P6069
|
FINISHED |
| Object | about 220 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 220 hp | Statement: [Waco UPF-7, enginePowerClass, about 220 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enginePowerClass Context triple: [Waco UPF-7, enginePowerClass, about 220 hp]
-
A.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
B.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
C.
hasEngineDisplacementClass
Indicates a relationship where a vehicle or engine is assigned to a category based on the size or volume of its engine displacement.
-
D.
powerClassBR
Indicates a relationship where one entity is classified or grouped according to its power-related category or level relative to another entity.
-
E.
vehiclePowerCollection
Indicates a relationship where a vehicle is associated with a set or collection of its power-related components, sources, or specifications.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e4756881909335e1e7b3c23e28 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.