Triple
T772011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holden Monaro |
E16301
|
entity |
| Predicate | notableEngine |
P4856
|
FINISHED |
| Object | 5.0 L Holden V8 |
—
|
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: 5.0 L Holden V8 | Statement: [Holden Monaro, notableEngine, 5.0 L Holden V8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEngine Context triple: [Holden Monaro, notableEngine, 5.0 L Holden V8]
-
A.
notableEngineType
chosen
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
B.
notableRobot
Indicates that the subject is a robot recognized for its significance, prominence, or special distinction.
-
C.
notableEditor
Indicates that an entity has served as a significant or distinguished editor of another entity, such as a publication or work.
-
D.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
-
E.
notableElement
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a706abf88190a1cbc2dfbbf9968a |
completed | March 1, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.