Triple
T5353531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granada War |
E102632
|
entity |
| Predicate | belligerentReligion |
P10155
|
FINISHED |
| Object | Roman Catholicism |
—
|
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: Roman Catholicism | Statement: [Granada War, belligerentReligion, Roman Catholicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belligerentReligion Context triple: [Granada War, belligerentReligion, Roman Catholicism]
-
A.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
B.
conflictBelligerent
chosen
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
C.
religiousConflictBetween
Indicates a relationship where two entities are in opposition or dispute due to differing religious beliefs, practices, or affiliations.
-
D.
belligerentInterest
Indicates that an entity has a hostile, aggressive, or conflict-seeking attitude or stake toward another entity or situation.
-
E.
religionOfPerpetrators
Indicates the religious affiliation or belief system associated with the individuals who carried out a particular act or offense.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86149774819084049a8785e3f2e0 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.