Triple
T25121172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Bannatyne |
E629269
|
entity |
| Predicate | hasManuscriptNamedAfter |
P134215
|
FINISHED |
| Object | Bannatyne Manuscript |
—
|
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: Bannatyne Manuscript | Statement: [George Bannatyne, hasManuscriptNamedAfter, Bannatyne Manuscript]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManuscriptNamedAfter Context triple: [George Bannatyne, hasManuscriptNamedAfter, Bannatyne Manuscript]
-
A.
areManuscriptsOf
Indicates that the subject entities are manuscripts that are versions, copies, or instances of the work represented by the object entity.
-
B.
manuscriptName
chosen
Indicates the name or title assigned to a manuscript in the relationship.
-
C.
manuscriptDiscoveredBy
Indicates that a manuscript was found or brought to light through the efforts or actions of a particular agent or entity.
-
D.
hasManuscriptsIn
Indicates that an entity possesses or is associated with manuscripts that are located in a specified place or collection.
-
E.
copiedManuscriptsOf
Indicates that one entity has produced or created handwritten reproductions of the manuscripts belonging to 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 18, 2026, 6:28 a.m.