Triple
T19687736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ante-Purgatory |
E472754
|
entity |
| Predicate | workCompositionCentury |
P41949
|
FINISHED |
| Object | 14th century |
—
|
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: 14th century | Statement: [Ante-Purgatory, workCompositionCentury, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCompositionCentury Context triple: [Ante-Purgatory, workCompositionCentury, 14th century]
-
A.
centuryOfWork
Indicates the century during which a particular work, activity, or contribution primarily took place.
-
B.
probableCenturyOfComposition
chosen
Indicates the century in which something (typically a work or composition) was most likely created or written.
-
C.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
D.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
E.
historicalComposition
Indicates that one entity was historically part of, or contributed to the makeup or structure of, another entity during a past period.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420d39688190ad3a84dbffce4ffe |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.