Triple
T18295930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A9X performance package |
E438229
|
entity |
| Predicate | manufacturer |
P490
|
FINISHED |
| Object | Holden |
—
|
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 | Statement: [A9X performance package, manufacturer, Holden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holden Context triple: [A9X performance package, manufacturer, Holden]
-
A.
Holden
Holden is a suburban town in Worcester County, Massachusetts, known for its residential character and proximity to the city of Worcester.
-
B.
Holden
Holden is a small city located in Johnson County, Missouri, in the United States.
-
C.
Holden
chosen
Holden was an Australian automobile manufacturer and marque owned by General Motors, known for producing popular locally designed cars before ceasing operations in the 21st century.
-
D.
Holden
Holden is a small town in central Utah, United States, known for its rural character and proximity to Interstate 15.
-
E.
Holden
Holden is a masculine given name of English origin, commonly used in English-speaking countries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017783748190905ce4eeadd25841 |
completed | April 19, 2026, 4:23 p.m. |
Created at: April 10, 2026, 10:35 a.m.