Triple
T23871977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortuna Imperatrix Mundi |
E592750
|
entity |
| Predicate | originalTextCentury |
P15335
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Fortuna Imperatrix Mundi, originalTextCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTextCentury Context triple: [Fortuna Imperatrix Mundi, originalTextCentury, 13th century]
-
A.
originalCentury
chosen
Indicates the century in which something was originally created, produced, or came into existence.
-
B.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
C.
centuryOfTranslation
Indicates the century during which a translation of a work or text was produced.
-
D.
revisedInCentury
Indicates that an existing work or entity was revised or updated during a specified century.
-
E.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfed81881909905f71377f759b1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.