Triple
T25364666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blessed |
E636065
|
entity |
| Predicate | titlePlacement |
P21675
|
FINISHED |
| Object | placed before personal name |
—
|
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: placed before personal name | Statement: [Blessed, titlePlacement, placed before personal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titlePlacement Context triple: [Blessed, titlePlacement, placed before personal name]
-
A.
titlePositionRelation
chosen
Indicates a relationship specifying how a title is positioned or ordered relative to other titles or elements.
-
B.
titleHolderAlignment
Indicates the alignment or affiliation associated with the current holder of a specific title or position.
-
C.
titleHolderStartPosition
Indicates the position in a sequence or ranking at which an entity begins holding a particular title.
-
D.
datePlacement
Indicates a temporal relationship specifying when an event or entity is positioned or scheduled in time, such as the assigned or actual date of occurrence.
-
E.
titleHolderSide
Indicates which side, party, or competitor currently holds a particular title in a contest, match, or competition.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 1:36 p.m.