Triple
T3439655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottonian Renaissance |
E72534
|
entity |
| Predicate | mainCenter |
P4751
|
FINISHED |
| Object | Saxon regions |
—
|
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: Saxon regions | Statement: [Ottonian Renaissance, mainCenter, Saxon regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCenter Context triple: [Ottonian Renaissance, mainCenter, Saxon regions]
-
A.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
C.
mainIndex
Indicates that one entity serves as the primary or central index or reference point for another entity within a structured system.
-
D.
centralText
Indicates that one text element is positioned or designated as the central or primary text relative to surrounding content or layout.
-
E.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f6de1481909b789f4b0e1113d3 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.