Triple
T31352286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGS |
E799629
|
entity |
| Predicate | notableWriterInUniverse |
P11016
|
FINISHED |
| Object | Liz Lemon |
E938299
|
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: Liz Lemon | Statement: [TGS, notableWriterInUniverse, Liz Lemon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWriterInUniverse Context triple: [TGS, notableWriterInUniverse, Liz Lemon]
-
A.
hasNotableWriter
Indicates that an entity is associated with a writer who is recognized as significant or distinguished in some notable way.
-
B.
notableAuthorMember
Indicates that an entity is a notable or distinguished author who is a member of a particular group, organization, or collection.
-
C.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
D.
notableAuthorConcept
Indicates that an author is notably associated with, influential in, or prominently recognized for work related to a particular concept.
-
E.
famousWriterAssociated
chosen
Indicates a relationship where a well-known or renowned writer is connected or linked to a particular entity (such as a work, place, event, or organization).
- F. None of above.
Provenance (4 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b561d51f08190bd358ea9ea13a2a1 |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:17 p.m.