Triple
T11420503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milwaukee-Eight engine |
E270604
|
entity |
| Predicate | primaryDisplacementVariant |
P99212
|
FINISHED |
| Object | 107 cubic inches |
—
|
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: 107 cubic inches | Statement: [Milwaukee-Eight engine, primaryDisplacementVariant, 107 cubic inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDisplacementVariant Context triple: [Milwaukee-Eight engine, primaryDisplacementVariant, 107 cubic inches]
-
A.
primaryVariant
Indicates that one entity is the main or canonical version among multiple related variants of another entity.
-
B.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
-
D.
primaryVariantInService
Indicates that a particular variant is the main or default version currently active or in use within a given service or system.
-
E.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
- F. None of above. chosen
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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b20ce08190befc98379b879985 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.