Triple
T20362565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Center Theatre Group |
E496817
|
entity |
| Predicate | hasExecutiveLeadership |
P36552
|
FINISHED |
| Object | managing 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: managing director | Statement: [Center Theatre Group, hasExecutiveLeadership, managing director]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutiveLeadership Context triple: [Center Theatre Group, hasExecutiveLeadership, managing director]
-
A.
haveExecutiveHead
Indicates that one entity serves as the executive leader or chief authority (e.g., CEO, president, head of government) of another entity.
-
B.
hasExecutiveHeadTitle
chosen
Indicates the official job title held by the person who serves as the executive head of an organization or entity.
-
C.
hadLeadershipFrom
Indicates that one entity received leadership, guidance, or direction from another entity.
-
D.
hasExecutiveAuthority
Indicates that one entity holds formal decision-making and managerial power over an organization, group, or process.
-
E.
hasTypeOfLeadership
Indicates that an entity possesses or is characterized by a specific style or form of leadership.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6786efd2c8190821932ddcdef1a2f |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:26 a.m.