Triple
T21442414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steely Dan III from Yokohama |
E528968
|
entity |
| Predicate | hasPerformingRole |
P42172
|
FINISHED |
| Object | live performance band |
—
|
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: live performance band | Statement: [Steely Dan III from Yokohama, hasPerformingRole, live performance band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformingRole Context triple: [Steely Dan III from Yokohama, hasPerformingRole, live performance band]
-
A.
hasHumanCharacterRole
Indicates that an entity is assigned a role or function specifically associated with a human character within a context such as a story, performance, or representation.
-
B.
playsInRole
chosen
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
C.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
D.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
E.
hasBelovedRole
Indicates that an entity holds a role or position that is deeply cherished or loved by another entity.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b70322bc8190ae693163ededf5a0 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.