Triple
T27107966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Opera |
E686631
|
entity |
| Predicate | hasGeneralDirector |
P63421
|
FINISHED |
| Object | Christina Scheppelmann |
—
|
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: Christina Scheppelmann | Statement: [Seattle Opera, hasGeneralDirector, Christina Scheppelmann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralDirector Context triple: [Seattle Opera, hasGeneralDirector, Christina Scheppelmann]
-
A.
generalDirector
chosen
Indicates that one entity serves as the general director (top executive or chief manager) of another entity, such as an organization or project.
-
B.
directorGeneralStart
Indicates the date or point in time when an individual begins serving as a director general of an organization or entity.
-
C.
hasPrimaryDirector
Indicates that an entity has a specific person or organization serving as its main or lead director.
-
D.
wirdGeleitetVon
Indicates that something (such as an organization, project, or process) is being led or directed by a specific person or entity.
-
E.
wasDirectorGeneralOf
Indicates that a person held the position of Director General of a specified organization or institution.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 8:52 a.m.