Triple
T14106981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Topaz |
E339531
|
entity |
| Predicate | offeredEngine |
P17976
|
FINISHED |
| Object | 2.3L inline-4 gasoline 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: 2.3L inline-4 gasoline engine | Statement: [Mercury Topaz, offeredEngine, 2.3L inline-4 gasoline engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredEngine Context triple: [Mercury Topaz, offeredEngine, 2.3L inline-4 gasoline engine]
-
A.
offeredEngineType
chosen
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
B.
offeredConfiguration
Indicates that one entity presents or makes available a specific configuration or setup option to another entity.
-
C.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
D.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
E.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600ada808190b92d67dc30f13d15 |
completed | April 14, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.