Triple
T5147734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fender Mike Dirnt Precision Bass |
E116114
|
entity |
| Predicate | hardwareFinish |
P61828
|
FINISHED |
| Object | chrome |
—
|
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: chrome | Statement: [Fender Mike Dirnt Precision Bass, hardwareFinish, chrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareFinish Context triple: [Fender Mike Dirnt Precision Bass, hardwareFinish, chrome]
-
A.
designCompletion
Indicates that the design phase of something has been finished or brought to completion.
-
B.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
C.
baseFinish
Indicates that one entity serves as the foundational or underlying finish or surface treatment upon which another finish or treatment is applied or built.
-
D.
hardwareIncluded
Indicates that certain hardware components are provided or come bundled together with another item or product.
-
E.
installationCompleted
Indicates that the process of installing something has finished successfully.
- F. None of above. chosen
Provenance (4 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:43 p.m.