Triple
T2353213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merkur XR4Ti |
E47493
|
entity |
| Predicate | layoutDescription |
P32581
|
FINISHED |
| Object | front-engine, rear-wheel-drive sport hatchback |
—
|
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, rear-wheel-drive sport hatchback | Statement: [Merkur XR4Ti, layoutDescription, front-engine, rear-wheel-drive sport hatchback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutDescription Context triple: [Merkur XR4Ti, layoutDescription, front-engine, rear-wheel-drive sport hatchback]
-
A.
layoutDetail
chosen
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
-
B.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
C.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
-
D.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abcb802da08190980100444010f91e |
completed | March 7, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69abc5981ce48190a3f7852d28276e11 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.