Triple
T34632164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMX (Javelin-based model 1971–1974) |
E889317
|
entity |
| Predicate | offeredWithEngineDisplacement |
P4162
|
FINISHED |
| Object | 304 cu in V8 |
—
|
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: 304 cu in V8 | Statement: [AMX (Javelin-based model 1971–1974), offeredWithEngineDisplacement, 304 cu in V8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredWithEngineDisplacement Context triple: [AMX (Javelin-based model 1971–1974), offeredWithEngineDisplacement, 304 cu in V8]
-
A.
availableEngineDisplacement
chosen
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
-
B.
engineDisplacement
Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
-
C.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
D.
hasEngineDisplacementClass
Indicates a relationship where a vehicle or engine is assigned to a category based on the size or volume of its engine displacement.
-
E.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 1, 2026, 2:04 a.m.