Triple
T5830054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Longsword |
E129321
|
entity |
| Predicate | titleAfterBaptism |
P26692
|
FINISHED |
| Object | Christian prince of Normandy |
—
|
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: Christian prince of Normandy | Statement: [William Longsword, titleAfterBaptism, Christian prince of Normandy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleAfterBaptism Context triple: [William Longsword, titleAfterBaptism, Christian prince of Normandy]
-
A.
titleAfterBeatification
Indicates the formal title or honorific that a person holds specifically after being beatified.
-
B.
baptismName
chosen
Indicates the name an individual receives or uses specifically in the context of a baptism ceremony.
-
C.
titleAfterNameChange
Indicates that the referenced title is the one held or used by an entity after a change to their name has occurred.
-
D.
baptized
Indicates that one entity performed or underwent the religious rite of baptism in relation to another entity or context.
-
E.
viewOnBaptism
Indicates a stance, belief, or doctrinal position that an entity holds regarding the practice or theology of baptism.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.