Triple
T31655439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craig Thomas |
E807846
|
entity |
| Predicate | partnerInWritingWith |
P49107
|
FINISHED |
| Object | Carter Bays |
—
|
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: Carter Bays | Statement: [Craig Thomas, partnerInWritingWith, Carter Bays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInWritingWith Context triple: [Craig Thomas, partnerInWritingWith, Carter Bays]
-
A.
writingPartner
chosen
Indicates a collaborative relationship in which two or more entities work together as co-authors or co-writers on written material.
-
B.
partnerInLiteraryLifeOf
Indicates a relationship where one entity is a significant companion or collaborator in another entity’s literary career or creative writing life.
-
C.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
D.
partnerInStory
Indicates that two or more entities are partners or collaborators within the context of a specific story or narrative.
-
E.
coAuthorField
Indicates that two or more entities have jointly authored a work within the same academic or professional field.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 30, 2026, 10:55 p.m.