Triple
T30083733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsfold |
E764542
|
entity |
| Predicate | isOftenPairedWithTextAuthor |
P8272
|
FINISHED |
| Object | Horatius Bonar |
—
|
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: Horatius Bonar | Statement: [Kingsfold, isOftenPairedWithTextAuthor, Horatius Bonar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenPairedWithTextAuthor Context triple: [Kingsfold, isOftenPairedWithTextAuthor, Horatius Bonar]
-
A.
partnerInLiteraryLifeOf
Indicates a relationship where one entity is a significant companion or collaborator in another entity’s literary career or creative writing life.
-
B.
associatedWithText
chosen
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
-
C.
authorOfCompanionWork
Indicates that one entity is the creator or writer of another entity that serves as a companion or supplementary work to a primary work.
-
D.
authorOfAlso
Indicates that an entity is also an author of another specified work or item, in addition to any primary authorship already indicated.
-
E.
hasCoauthor
Indicates that two or more entities have jointly authored the same 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d6a9ae08190ba91cbe92980e3f0 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:03 p.m.