Triple
T9993044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish medieval chronicles |
E196935
|
entity |
| Predicate | typicalAuthor |
P5464
|
FINISHED |
| Object | monk |
—
|
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: monk | Statement: [Scottish medieval chronicles, typicalAuthor, monk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAuthor Context triple: [Scottish medieval chronicles, typicalAuthor, monk]
-
A.
traditionalAuthor
chosen
Indicates that an entity is regarded as the conventional or historically accepted author of a work, even if actual authorship may be uncertain or disputed.
-
B.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
C.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
-
D.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
E.
traditionalAuthorship
Indicates that an entity is recognized as the conventional or historically accepted author of a work, according to traditional attribution.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcb96c7308190902802ef5df764c1 |
completed | April 2, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.