Triple
T31352283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGS |
E799629
|
entity |
| Predicate | executiveOversightBy |
P20679
|
FINISHED |
| Object | Jack Donaghy |
—
|
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: Jack Donaghy | Statement: [TGS, executiveOversightBy, Jack Donaghy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executiveOversightBy Context triple: [TGS, executiveOversightBy, Jack Donaghy]
-
A.
oversightOfficial
Indicates that one entity has formal responsibility for supervising, monitoring, or reviewing the actions or performance of another entity.
-
B.
oversee
chosen
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
C.
headOfGovernmentOversight
Indicates that one entity holds primary responsibility for supervising, directing, or managing the governmental activities or operations of another entity.
-
D.
oversawPolicy
Indicates that one entity had supervisory or managerial responsibility for the creation, implementation, or maintenance of a policy affecting another entity or domain.
-
E.
hasSecurityOversightBy
Indicates that the security responsibilities, controls, or governance for one entity are overseen, managed, or supervised by another entity.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:17 p.m.