Triple
T25510904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roat |
E639374
|
entity |
| Predicate | basedOnAuthorContext |
P2806
|
FINISHED |
| Object | Frederick Knott |
—
|
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: Frederick Knott | Statement: [Roat, basedOnAuthorContext, Frederick Knott]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnAuthorContext Context triple: [Roat, basedOnAuthorContext, Frederick Knott]
-
A.
basedOnAuthor
chosen
Indicates that one entity is derived from, inspired by, or otherwise created on the basis of the work or contributions of a particular author.
-
B.
publicationAuthorContext
Indicates the contextual relationship between a publication and its author(s), such as roles, contributions, or circumstances under which the work was created.
-
C.
basedOnSubject
Indicates that something is derived from, influenced by, or determined according to a particular subject.
-
D.
basedOnText
Indicates that something is derived, adapted, or developed from a specific text source.
-
E.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 2:49 p.m.