Triple
T2273903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boss 429 |
E50723
|
entity |
| Predicate | frontShockTowers |
P37626
|
FINISHED |
| Object | relocated for engine clearance |
—
|
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: relocated for engine clearance | Statement: [Boss 429, frontShockTowers, relocated for engine clearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontShockTowers Context triple: [Boss 429, frontShockTowers, relocated for engine clearance]
-
A.
suspensionRear
Indicates that the relationship or action involves the rear suspension component or system of an object, typically a vehicle.
-
B.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
C.
suspensionType
Indicates the specific kind or configuration of suspension system associated with an entity (e.g., a vehicle or structure).
-
D.
frontSector
Indicates that one entity is located in the forward-facing sector or region relative to another entity.
-
E.
spurType
Indicates the specific kind or category of spur associated with or used by an entity.
- F. None of above. chosen
Provenance (4 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc39c6ff0819081a07696f1c29990 |
completed | March 7, 2026, 6:20 a.m. |
| PD | Predicate disambiguation | batch_69abbdb7719081909143efa8f48df4e4 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abc39b2f548190a38f604e0d36db3a |
completed | March 7, 2026, 6:20 a.m. |
Created at: March 4, 2026, 7:48 p.m.