Triple
T23918443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truce of God |
E602143
|
entity |
| Predicate | wasEnforcedBy |
P104153
|
FINISHED |
| Object | ecclesiastical sanctions |
—
|
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: ecclesiastical sanctions | Statement: [Truce of God, wasEnforcedBy, ecclesiastical sanctions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEnforcedBy Context triple: [Truce of God, wasEnforcedBy, ecclesiastical sanctions]
-
A.
alsoEnforcedBy
chosen
Indicates that the same rule, policy, or constraint is enforced by an additional authority, mechanism, or entity beyond the primary one.
-
B.
originallyEnforcedBy
Indicates that a rule, law, policy, or agreement was first implemented and upheld by a particular enforcing authority or agent.
-
C.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
-
D.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
E.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1600248190b38cfc93afb22a73 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:41 p.m.