Triple
T29283986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Danish Ballet |
E742457
|
entity |
| Predicate | hasNotableDancerAlumni |
P17435
|
FINISHED |
| Object | Erik Bruhn |
—
|
NE NERFINISHED |
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: Erik Bruhn | Statement: [Royal Danish Ballet, hasNotableDancerAlumni, Erik Bruhn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDancerAlumni Context triple: [Royal Danish Ballet, hasNotableDancerAlumni, Erik Bruhn]
-
A.
hasNotableAlumniType
Indicates that an entity has notable alumni belonging to a specified category or type.
-
B.
hasNotableAlumniInstitution
Indicates that an institution is associated with one or more notable alumni who previously attended or graduated from it.
-
C.
hasNotableFacultyAlumnus
Indicates that an individual is a distinguished former student who is recognized as notable faculty at a given institution.
-
D.
featuredDancers
Indicates that certain dancers are highlighted or given special prominence in a performance, event, or context.
-
E.
hasNotablePerformer
chosen
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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: April 28, 2026, 12:56 p.m.