Triple
T23852560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Model 18 |
E592211
|
entity |
| Predicate | introducedEngineType |
P141160
|
FINISHED |
| Object | Ford flathead V8 |
—
|
NE NERFINISHED |
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: Ford flathead V8 | Statement: [Ford Model 18, introducedEngineType, Ford flathead V8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedEngineType Context triple: [Ford Model 18, introducedEngineType, Ford flathead V8]
-
A.
engineIntroduced
Indicates that a particular engine was first introduced or brought into use at a specific time or in a specific context.
-
B.
originalEngineType
chosen
Indicates the type or category of engine that an entity was initially or first equipped with.
-
C.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
-
D.
engineTypeBuilt
Indicates that a specific type of engine has been constructed or manufactured by a particular entity.
-
E.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c9887e5c819089437769acf684c4 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.