Triple
T8709079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eusebius of Nicomedia |
E206726
|
entity |
| Predicate | courtPosition |
P22449
|
FINISHED |
| Object | influential prelate at the imperial court |
—
|
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: influential prelate at the imperial court | Statement: [Eusebius of Nicomedia, courtPosition, influential prelate at the imperial court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtPosition Context triple: [Eusebius of Nicomedia, courtPosition, influential prelate at the imperial court]
-
A.
courtRole
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
-
B.
courtOfficial
Indicates that an entity serves in an official capacity within a court, holding an authorized role in judicial or legal proceedings.
-
C.
positionInCourt
chosen
Indicates the specific role or standing an entity holds within a court setting or judicial proceeding.
-
D.
positionOnLaw
Indicates a stance, opinion, or interpretation that an entity holds regarding a specific law or legal provision.
-
E.
courtRank
Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c2e9c688190aceefaa2c3b7d7bd |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.