Triple
T31384185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geva Theatre Center |
E800550
|
entity |
| Predicate | hasExecutiveLeadershipRole |
P87815
|
FINISHED |
| Object | Executive Director |
—
|
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: Executive Director | Statement: [Geva Theatre Center, hasExecutiveLeadershipRole, Executive Director]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutiveLeadershipRole Context triple: [Geva Theatre Center, hasExecutiveLeadershipRole, Executive Director]
-
A.
roleInExecutive
chosen
Indicates that an entity holds a specific position or function within an executive body or leadership structure.
-
B.
haveExecutiveHead
Indicates that one entity serves as the executive leader or chief authority (e.g., CEO, president, head of government) of another entity.
-
C.
hasExecutiveHeadTitle
Indicates the official job title held by the person who serves as the executive head of an organization or entity.
-
D.
hasExecutiveAuthority
Indicates that one entity holds formal decision-making and managerial power over an organization, group, or process.
-
E.
hasExecutivePartner
Indicates that an entity has a business partner with executive-level authority or status within the partnership.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 9:19 p.m.