Triple
T31352245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGS writers’ room |
E799628
|
entity |
| Predicate | createdByWorkCreator |
P197134
|
FINISHED |
| Object | Tina Fey |
E11671
|
NE 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: Tina Fey | Statement: [TGS writers’ room, createdByWorkCreator, Tina Fey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByWorkCreator Context triple: [TGS writers’ room, createdByWorkCreator, Tina Fey]
-
A.
createdForWorkBy
Indicates that something was created specifically for use in work or professional activities by a particular agent or person.
-
B.
hasWorkCreator
Indicates that an entity is the creator or originator of a particular work (such as a document, artwork, or other creative product).
-
C.
createdWork
Indicates that an agent is responsible for bringing a work (such as a creative, intellectual, or produced artifact) into existence.
-
D.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
E.
relatedWorkCreator
Indicates that the creator of one work is related (e.g., by authorship, contribution, or collaboration) to the creation of another work.
- F. None of above. chosen
Provenance (5 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_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b561d51f08190bd358ea9ea13a2a1 |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
| PDg | Predicate description generation | batch_69fe78e35e6c8190b8b440777912f64e |
completed | May 8, 2026, 11:59 p.m. |
Created at: April 29, 2026, 9:17 p.m.