Triple
T30700224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joffrey Ballet |
E781589
|
entity |
| Predicate | hasNotableChoreographer |
P151877
|
FINISHED |
| Object | Gerald Arpino |
—
|
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: Gerald Arpino | Statement: [Joffrey Ballet, hasNotableChoreographer, Gerald Arpino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableChoreographer Context triple: [Joffrey Ballet, hasNotableChoreographer, Gerald Arpino]
-
A.
hasNotableChoreographerAssociation
chosen
Indicates a relationship where an entity is significantly associated with a particular choreographer, such as through collaboration, influence, or dedicated work.
-
B.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
C.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
D.
hasNotableCrewMember
Indicates that an entity is associated with a crew member who is considered notable or distinguished in some way.
-
E.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 29, 2026, 8:34 p.m.