Triple
T23600517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reginald FitzUrse |
E582738
|
entity |
| Predicate | afterEventConsequence |
P812
|
FINISHED |
| Object | excommunication |
—
|
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: excommunication | Statement: [Reginald FitzUrse, afterEventConsequence, excommunication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterEventConsequence Context triple: [Reginald FitzUrse, afterEventConsequence, excommunication]
-
A.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
aftermathOf
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
C.
aftermathActivity
Indicates the activity or state that occurs as a direct consequence of, or in response to, a preceding event or situation.
-
D.
significantEventConsequence
Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
-
E.
aftermathDescription
Indicates the description or characterization of events, conditions, or consequences that occur following a particular incident or action.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0936f588190aead4419aedfcb0e |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:43 p.m.