Triple
T27697553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Dormans |
E698338
|
entity |
| Predicate | opponentReligiousAffiliation |
P28124
|
FINISHED |
| Object | Reformed |
—
|
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: Reformed | Statement: [Battle of Dormans, opponentReligiousAffiliation, Reformed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentReligiousAffiliation Context triple: [Battle of Dormans, opponentReligiousAffiliation, Reformed]
-
A.
primaryOpponentsReligion
chosen
Indicates the religion or belief system followed by an entity’s main or primary opponent.
-
B.
otherRivalReligion
Indicates that one entity follows or is associated with a religion that is a rival or competing faith to the religion associated with another entity.
-
C.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
E.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:55 p.m.