Triple
T26195255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankenstrat guitar |
E655078
|
entity |
| Predicate | bridgePickupPosition |
P61800
|
FINISHED |
| Object | bridge |
—
|
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: bridge | Statement: [Frankenstrat guitar, bridgePickupPosition, bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgePickupPosition Context triple: [Frankenstrat guitar, bridgePickupPosition, bridge]
-
A.
bridgePickupType
Indicates the specific method or configuration by which the bridge pickup operates or is used in relation to the instrument.
-
B.
bridgePickupOrigin
Indicates that an entity serves as the original pickup location in a bridge or intermediary transfer process between two points.
-
C.
bridgePosition
chosen
Indicates the spatial or structural position of a bridge relative to other referenced elements or locations.
-
D.
pickupConfiguration
Indicates the specific arrangement or setup in which one entity is collected, retrieved, or picked up by another.
-
E.
pickupOption
Indicates that one entity offers or selects a method or arrangement for collecting or retrieving another entity (such as goods, items, or services).
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca5cd78819083f0216b359da470 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 8:46 p.m.