Triple
T9328573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astaire–Rogers dance partnership |
E224457
|
entity |
| Predicate | hasMainPerformerRole |
P50979
|
FINISHED |
| Object | dancer |
—
|
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: dancer | Statement: [Astaire–Rogers dance partnership, hasMainPerformerRole, dancer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPerformerRole Context triple: [Astaire–Rogers dance partnership, hasMainPerformerRole, dancer]
-
A.
hasMainPerformerOccupation
chosen
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
-
B.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
C.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
D.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
E.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ab90ac8190b5c73f08dd091731 |
completed | April 1, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.