Triple
T23871983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortuna Imperatrix Mundi |
E592750
|
entity |
| Predicate | textTopic |
P26448
|
FINISHED |
| Object | wheel of fortune |
—
|
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: wheel of fortune | Statement: [Fortuna Imperatrix Mundi, textTopic, wheel of fortune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textTopic Context triple: [Fortuna Imperatrix Mundi, textTopic, wheel of fortune]
-
A.
featuresTopic
chosen
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
-
B.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
C.
coveredTopics
Indicates that certain subjects or themes have been addressed or included within a discussion, document, or activity.
-
D.
topicOfDialogue
Indicates that a particular subject or theme is the main focus of a dialogue or conversation between entities.
-
E.
PSATopic
Indicates that one entity serves as the subject, theme, or focus of a public service announcement related to the other 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_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.