Triple
T4856197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares armoured personnel carrier |
E108541
|
entity |
| Predicate | hasEnginePosition |
P22132
|
FINISHED |
| Object | front-mounted engine compartment |
—
|
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: front-mounted engine compartment | Statement: [Ares armoured personnel carrier, hasEnginePosition, front-mounted engine compartment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnginePosition Context triple: [Ares armoured personnel carrier, hasEnginePosition, front-mounted engine compartment]
-
A.
hasEngineProgram
Indicates that an entity is associated with or participates in a specific engine-related program.
-
B.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
C.
enginePlacement
chosen
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
D.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
E.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.