Triple
T26664847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Rankine |
E672153
|
entity |
| Predicate | isMentionedInWorkBy |
P80280
|
FINISHED |
| Object | Robert Burns |
—
|
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: Robert Burns | Statement: [John Rankine, isMentionedInWorkBy, Robert Burns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMentionedInWorkBy Context triple: [John Rankine, isMentionedInWorkBy, Robert Burns]
-
A.
appearsInWorkByAuthorFrom
Indicates that an entity appears in a work that was created by an author originating from a specified place or country.
-
B.
discussedInWorkOf
chosen
Indicates that a subject is examined, treated, or talked about within a particular work or publication.
-
C.
attestedInWorksOf
Indicates that something (such as a claim, form, or usage) is documented or evidenced within the works produced by a particular author or creator.
-
D.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
E.
hasAuthorOfKeyWork
Indicates that an entity serves as the author or creator of a significant or primary work associated with another entity.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f616c278b48190a1c1dc7a07a77ced |
completed | May 2, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:08 a.m.