Triple
T30807280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Opera Ballet |
E784538
|
entity |
| Predicate | employedDancer |
P79355
|
FINISHED |
| Object | Marjorie Tallchief |
—
|
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: Marjorie Tallchief | Statement: [Chicago Opera Ballet, employedDancer, Marjorie Tallchief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedDancer Context triple: [Chicago Opera Ballet, employedDancer, Marjorie Tallchief]
-
A.
featuresProfessionalDancer
chosen
Indicates that an entity includes or presents a professional dancer as part of its content, composition, or offering.
-
B.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
C.
employedThrough
Indicates that an entity holds a job or work position by means of, or via the arrangement of, another entity (such as an agency, contractor, or intermediary).
-
D.
alsoDancedAs
Indicates that an entity performed under an additional dance name or identity besides their primary one.
-
E.
employedActor
Indicates that one entity has hired or currently employs another entity to perform work or services.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 8:43 p.m.