Triple
T1084747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dei Filius |
E24023
|
entity |
| Predicate | magisterialLevel |
P14652
|
FINISHED |
| Object | solemn |
—
|
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: solemn | Statement: [Dei Filius, magisterialLevel, solemn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magisterialLevel Context triple: [Dei Filius, magisterialLevel, solemn]
-
A.
magisterialType
Indicates the specific kind or category of magisterial authority, jurisdiction, or court associated with an entity.
-
B.
magisterialStatus
Indicates that an entity holds or is assigned a formal magisterial (official judicial or administrative) authority or status in relation to another entity or context.
-
C.
grandMaster
Indicates that one entity holds the highest authoritative or mastery status over a domain, discipline, or organization in relation to another entity.
-
D.
majorPass
Indicates that an entity successfully completes or passes a significant or primary stage, requirement, or examination in relation to another entity or process.
-
E.
ecclesiasticalLevel
chosen
Indicates the hierarchical rank or status of an entity within an ecclesiastical (church) organization.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9608bac819085196cc0f8fbb2e7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.