Triple
T4454079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fender Stratocaster |
E97679
|
entity |
| Predicate | originalPickupSelector |
P56616
|
FINISHED |
| Object | 3-way switch |
—
|
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: 3-way switch | Statement: [Fender Stratocaster, originalPickupSelector, 3-way switch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPickupSelector Context triple: [Fender Stratocaster, originalPickupSelector, 3-way switch]
-
A.
pickupConfiguration
Indicates the specific arrangement or setup in which one entity is collected, retrieved, or picked up by another.
-
B.
pickupOption
Indicates that one entity offers or selects a method or arrangement for collecting or retrieving another entity (such as goods, items, or services).
-
C.
dropOffOptions
Indicates the available ways, locations, or conditions under which something can be dropped off or delivered.
-
D.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
-
E.
dropOffOption
Indicates an available method or arrangement by which something can be left or delivered at a specified location.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355f669948190b14ef42e8dbca525 |
completed | March 13, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b354e1f0948190b645096b2b7037af |
completed | March 13, 2026, 12:05 a.m. |
Created at: March 12, 2026, 11:33 p.m.