Triple
T17086732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papal Crusade |
E414616
|
entity |
| Predicate | hasPrimaryReligionTarget |
P6432
|
FINISHED |
| Object | non-Christians |
—
|
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: non-Christians | Statement: [Papal Crusade, hasPrimaryReligionTarget, non-Christians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryReligionTarget Context triple: [Papal Crusade, hasPrimaryReligionTarget, non-Christians]
-
A.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
B.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
C.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
D.
majorReligionCanBe
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
-
E.
religiousTarget
chosen
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe7ccb48190b8fb39e2a0ba0782 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.