Triple
T8485578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born This Way |
E200823
|
entity |
| Predicate | prominentInstrument |
P54631
|
FINISHED |
| Object | synthesizer |
—
|
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: synthesizer | Statement: [Born This Way, prominentInstrument, synthesizer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentInstrument Context triple: [Born This Way, prominentInstrument, synthesizer]
-
A.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
B.
featuresPrimaryInstrument
chosen
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
-
C.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
D.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
-
E.
primaryInstrumentAbbreviation
Indicates that one entity is the standard shortened or abbreviated form of the name of another entity’s primary instrument.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53b359c81908174addcd6e12785 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.