Triple
T31802362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prüm Abbey |
E811774
|
entity |
| Predicate | receivedRoyalProtectionFrom |
P957
|
FINISHED |
| Object | Louis the Pious |
—
|
NE NERFINISHED |
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: Louis the Pious | Statement: [Prüm Abbey, receivedRoyalProtectionFrom, Louis the Pious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedRoyalProtectionFrom Context triple: [Prüm Abbey, receivedRoyalProtectionFrom, Louis the Pious]
-
A.
receivedSilverHandFrom
Indicates that one entity was given or awarded a "Silver Hand" (e.g., a title, artifact, or honor) by another entity.
-
B.
protectedBy
chosen
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
receivedImmunityFrom
Indicates that one entity has been granted protection or exemption (such as legal, medical, or other forms of immunity) by another entity.
-
D.
securedThroneBy
Indicates that one entity obtained or maintained a throne or rulership position through the actions, support, or intervention of another entity.
-
E.
grantedHonor
Indicates that one entity has formally bestowed an honor, award, or distinction upon another 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 30, 2026, 11:42 p.m.