Triple
T34436632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Walker |
E883974
|
entity |
| Predicate | hasCoWriterOfWork |
P173708
|
FINISHED |
| Object | John Byrum |
E975754
|
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: John Byrum | Statement: [Brian Walker, hasCoWriterOfWork, John Byrum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoWriterOfWork Context triple: [Brian Walker, hasCoWriterOfWork, John Byrum]
-
A.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
B.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
C.
hasAuthorOfSameWorkAs
chosen
Indicates that two authors are related by having written or contributed to the same work.
-
D.
hasWriterOfWork
Indicates that a person or entity is the writer/author who created a particular work (such as a book, article, or script).
-
E.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37792d07d48190bc0bc79d772eb386 |
completed | June 21, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.