Triple
T31534615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluebird pas de deux |
E804570
|
entity |
| Predicate | iconicRoleFor |
P171931
|
FINISHED |
| Object | male classical dancers |
—
|
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: male classical dancers | Statement: [Bluebird pas de deux, iconicRoleFor, male classical dancers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconicRoleFor Context triple: [Bluebird pas de deux, iconicRoleFor, male classical dancers]
-
A.
famousRole
Indicates that an entity is best known for portraying or performing a particular role or character.
-
B.
knownForRoleIn
Indicates that an entity is recognized or notable for performing a particular role in a specific work, project, or context.
-
C.
iconicTrait
Indicates that a trait is emblematic or strongly characteristic of an entity, making it widely recognized as a defining feature of that entity.
-
D.
hasFamousNamesakeRole
Indicates that an entity has a role or position that shares its name with a well-known or historically notable person.
-
E.
creditedRoleOf
Indicates that a particular role or position is formally acknowledged as being held or performed by a specific entity in a credit or attribution context.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:03 p.m.