Triple
T31401875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish medieval chronicles |
E801015
|
entity |
| Predicate | typicalAuthorship |
P207420
|
FINISHED |
| Object | clerics |
—
|
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: clerics | Statement: [Swedish medieval chronicles, typicalAuthorship, clerics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAuthorship Context triple: [Swedish medieval chronicles, typicalAuthorship, clerics]
-
A.
traditionalAuthorship
Indicates that an entity is recognized as the conventional or historically accepted author of a work, according to traditional attribution.
-
B.
traditionalAuthor
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.
-
C.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
D.
authorStyle
Indicates the stylistic characteristics or manner of expression associated with a particular author in their works.
-
E.
formOfAuthorship
Indicates the specific way in which an entity is credited as the creator or contributor to a work (e.g., author, editor, translator).
- F. None of above. chosen
Provenance (4 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:20 p.m.