Triple
T10461074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herndon’s Life of Lincoln |
E246674
|
entity |
| Predicate | coAuthorRoleOfJesseWWeik |
P45538
|
FINISHED |
| Object | editor and collaborator |
—
|
LITERAL 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: editor and collaborator | Statement: [Herndon’s Life of Lincoln, coAuthorRoleOfJesseWWeik, editor and collaborator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAuthorRoleOfJesseWWeik Context triple: [Herndon’s Life of Lincoln, coAuthorRoleOfJesseWWeik, editor and collaborator]
-
A.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
B.
coAuthorshipType
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
-
C.
coCreator
Indicates that two or more entities jointly created or produced something together.
-
D.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
E.
collaboratorRole
chosen
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50883b62c819082711b8c9fd968e3 |
completed | April 7, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:19 p.m.