Triple
T28651945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modular Transverse Matrix |
E725222
|
entity |
| Predicate | firstUsedInModel |
P20170
|
FINISHED |
| Object | Volkswagen Golf Mk7 |
—
|
NE NERFINISHED |
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: Volkswagen Golf Mk7 | Statement: [Modular Transverse Matrix, firstUsedInModel, Volkswagen Golf Mk7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedInModel Context triple: [Modular Transverse Matrix, firstUsedInModel, Volkswagen Golf Mk7]
-
A.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
B.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
C.
firstUsedOn
chosen
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
D.
firstUsedInEvent
Indicates that something (such as an object, method, or concept) was used for the first time during a specified event.
-
E.
firstUsedBy
Indicates that something was initially utilized, applied, or employed by a particular entity before any others.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: April 28, 2026, 4:52 a.m.