Triple
T37268778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand American Touring |
E924456
|
entity |
| Predicate | typicalEngineFamily |
P18926
|
FINISHED |
| Object | Milwaukee-Eight |
E270604
|
NE 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: Milwaukee-Eight | Statement: [Grand American Touring, typicalEngineFamily, Milwaukee-Eight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEngineFamily Context triple: [Grand American Touring, typicalEngineFamily, Milwaukee-Eight]
-
A.
typicalEngine
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
B.
notableEngineFamily
chosen
Indicates that one entity is a well-known or significant engine family associated with the other entity.
-
C.
typicalEngineCharacteristic
Indicates that the specified property or feature is a characteristic commonly or typically associated with the given engine.
-
D.
belongsToEngineFamily
Indicates that an engine is a member of, or classified under, a specific engine family or series.
-
E.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
- F. None of above.
Provenance (4 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a406384b5f88190aaec313f92b30022 |
completed | June 27, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.