Triple
T34230837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undermajordomo Minor |
E878185
|
entity |
| Predicate | authorOfWorkBefore |
P92731
|
FINISHED |
| Object | Patrick deWitt |
—
|
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: Patrick deWitt | Statement: [Undermajordomo Minor, authorOfWorkBefore, Patrick deWitt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOfWorkBefore Context triple: [Undermajordomo Minor, authorOfWorkBefore, Patrick deWitt]
-
A.
authorOfPreviousWork
chosen
Indicates that one entity is the creator or writer of an earlier work referenced or built upon by another entity.
-
B.
literaryPredecessor
Indicates that one work of literature precedes and influences another in a historically or artistically significant way.
-
C.
chronologyPreviousWorkOf
Indicates that one work temporally precedes and is part of the earlier sequence in the overall body of another work.
-
D.
authorOfWorkAbout
Indicates that one entity is the author or creator of a work whose subject or content is about another entity.
-
E.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.