Triple
T5628409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fender Telecaster |
E147775
|
entity |
| Predicate | bridgePickupType |
P65512
|
FINISHED |
| Object | single-coil |
—
|
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: single-coil | Statement: [Fender Telecaster, bridgePickupType, single-coil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgePickupType Context triple: [Fender Telecaster, bridgePickupType, single-coil]
-
A.
pickupType
Indicates the manner or method by which an item or person is collected or retrieved (e.g., in-store pickup, curbside, scheduled pickup).
-
B.
typicalPickupType
Indicates the usual or standard method by which an item or order is collected or picked up.
-
C.
pickupOption
Indicates that one entity offers or selects a method or arrangement for collecting or retrieving another entity (such as goods, items, or services).
-
D.
pickupConfiguration
Indicates the specific arrangement or setup in which one entity is collected, retrieved, or picked up by another.
-
E.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0223b1e54819099fe5fc84ed17a88 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f40df64819089a659ea00a835ef |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.