Triple
T3590869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorabilia |
E76021
|
entity |
| Predicate | defendsAgainst |
P6876
|
FINISHED |
| Object | charges of impiety |
—
|
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: charges of impiety | Statement: [Memorabilia, defendsAgainst, charges of impiety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendsAgainst Context triple: [Memorabilia, defendsAgainst, charges of impiety]
-
A.
defends
chosen
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
B.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
C.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
D.
defenceHandledBy
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
-
E.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1581278819081dd73b4c71e422e |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.