Triple
T28196617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Special |
E716465
|
entity |
| Predicate | wiringFeatures |
P164121
|
FINISHED |
| Object | individual on-off switches for each pickup |
—
|
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: individual on-off switches for each pickup | Statement: [Red Special, wiringFeatures, individual on-off switches for each pickup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wiringFeatures Context triple: [Red Special, wiringFeatures, individual on-off switches for each pickup]
-
A.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
B.
numberOfWires
Indicates the quantity of wires associated with or contained in a given entity.
-
C.
isWired
Indicates that one entity is physically connected to another via electrical or data wiring.
-
D.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
E.
includesWireless
Indicates that one entity provides or comes equipped with wireless capability, connectivity, or components for another entity.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642d23ea481908f010394a925b83f |
completed | May 2, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:28 p.m.