Triple
T30633716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauche the Cellist |
E779776
|
entity |
| Predicate | centralInstrument |
P26810
|
FINISHED |
| Object | cello |
—
|
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: cello | Statement: [Gauche the Cellist, centralInstrument, cello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralInstrument Context triple: [Gauche the Cellist, centralInstrument, cello]
-
A.
coreInstrument
chosen
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
B.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
centralSet
Indicates that the referenced set occupies a central or core position within a larger structure, system, or collection, often serving as a primary or focal subset.
-
D.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
E.
coInstrumentWith
Indicates that two or more entities are used together as instruments or means to perform the same action or achieve the same outcome.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 29, 2026, 8:28 p.m.