Triple
T23918458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truce of God |
E602143
|
entity |
| Predicate | restrictedWarfareOn |
P154358
|
FINISHED |
| Object | Sundays |
—
|
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: Sundays | Statement: [Truce of God, restrictedWarfareOn, Sundays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restrictedWarfareOn Context triple: [Truce of God, restrictedWarfareOn, Sundays]
-
A.
opposedWarfareType
Indicates that one entity is in opposition to, or acts against, the type or form of warfare represented by the other entity.
-
B.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
C.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
D.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
E.
opposedByMilitaryForce
Indicates that one party’s actions, plans, or presence are actively resisted or countered through the use or threat of military force by another party.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:41 p.m.