Triple
T11263281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cudahy |
E266617
|
entity |
| Predicate | hasExecutiveOfficial |
P50969
|
FINISHED |
| Object | mayor |
—
|
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: mayor | Statement: [Cudahy, hasExecutiveOfficial, mayor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutiveOfficial Context triple: [Cudahy, hasExecutiveOfficial, mayor]
-
A.
hasNationalExecutive
Indicates that an entity possesses or is associated with a national-level executive authority or governing body.
-
B.
hasExecutiveAuthority
Indicates that one entity holds formal decision-making and managerial power over an organization, group, or process.
-
C.
hasExecutiveSeat
Indicates that an entity holds a position or seat with executive authority or decision-making power within an organization or governing body.
-
D.
haveExecutiveHead
chosen
Indicates that one entity serves as the executive leader or chief authority (e.g., CEO, president, head of government) of another entity.
-
E.
hasChiefExecutiveRole
Indicates that an entity holds the highest executive leadership position and overall managerial authority within an organization.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94d56048190bf808e1bc2188714 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.