Triple
T23013338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USF Pro 2000 Championship |
E572963
|
entity |
| Predicate | typicalCarPower |
P89369
|
FINISHED |
| Object | approximately 275 horsepower |
—
|
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: approximately 275 horsepower | Statement: [USF Pro 2000 Championship, typicalCarPower, approximately 275 horsepower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCarPower Context triple: [USF Pro 2000 Championship, typicalCarPower, approximately 275 horsepower]
-
A.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
B.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
C.
vehiclePowerCollection
Indicates a relationship where a vehicle is associated with a set or collection of its power-related components, sources, or specifications.
-
D.
typicalPower
chosen
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
-
E.
winnerPowertrainType
Indicates the type of powertrain used by the entity that is identified as the winner in a given context or competition.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e300008190bb12c6388a8b3280 |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.