Triple
T24801376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeep Wrangler Rubicon |
E620531
|
entity |
| Predicate | availableEngineType |
P17976
|
FINISHED |
| Object | inline-four 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-four engine | Statement: [Jeep Wrangler Rubicon, availableEngineType, inline-four engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableEngineType Context triple: [Jeep Wrangler Rubicon, availableEngineType, inline-four engine]
-
A.
offeredEngineType
chosen
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
B.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
-
D.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
-
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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f412aacd388190aa3cae919d6bdee2 |
completed | May 1, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:49 a.m.