Triple
T6807678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfa Romeo 164 |
E156348
|
entity |
| Predicate | layoutVariant |
P39487
|
FINISHED |
| Object | front-engine, front-wheel drive |
—
|
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-engine, front-wheel drive | Statement: [Alfa Romeo 164, layoutVariant, front-engine, front-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutVariant Context triple: [Alfa Romeo 164, layoutVariant, front-engine, front-wheel drive]
-
A.
layoutOptions
Indicates how elements are arranged or positioned relative to each other within a given space or structure.
-
B.
layoutDetail
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
-
C.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
-
D.
rulesVariantOf
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
-
E.
designVariant
chosen
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30b56c48190a5b244ea7e0c669a |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.