Triple
T35506997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holden V platform |
E1026175
|
entity |
| Predicate | usedInModelGeneration |
P37630
|
FINISHED |
| Object | Holden Commodore (VR) |
—
|
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: Holden Commodore (VR) | Statement: [Holden V platform, usedInModelGeneration, Holden Commodore (VR)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInModelGeneration Context triple: [Holden V platform, usedInModelGeneration, Holden Commodore (VR)]
-
A.
usedToModel
Indicates that one entity serves as a model or representation for another entity, typically for purposes of analysis, simulation, or understanding.
-
B.
usedByModel
Indicates that something (such as a resource, method, or component) is utilized or consumed by a particular model.
-
C.
usedInModelRange
Indicates that something (such as a component, parameter, or value) is utilized within the defined range or scope of a particular model.
-
D.
associatedModelGeneration
chosen
Indicates that one entity is responsible for creating, producing, or generating another related model or representation.
-
E.
useOfModel
Indicates that one entity employs, applies, or relies on a particular model for a specific purpose or task.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 3, 2026, 4:04 p.m.