Triple
T35752050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talbot-Lago |
E1033343
|
entity |
| Predicate | engineConfigurationUsed |
P56323
|
FINISHED |
| Object | inline-6 engine |
—
|
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: inline-6 engine | Statement: [Talbot-Lago, engineConfigurationUsed, inline-6 engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineConfigurationUsed Context triple: [Talbot-Lago, engineConfigurationUsed, inline-6 engine]
-
A.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
B.
engineTypeUsed
chosen
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
C.
combustionEngineConfiguration
Indicates the specific arrangement and setup of components and operating parameters within a combustion engine.
-
D.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
-
E.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a197aee48190bbd69f670a3f7721 |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.