Triple
T29742463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ayn Shams |
E752647
|
entity |
| Predicate | religiousContextSide1 |
P63841
|
FINISHED |
| Object | Muslim |
—
|
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: Muslim | Statement: [Battle of Ayn Shams, religiousContextSide1, Muslim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousContextSide1 Context triple: [Battle of Ayn Shams, religiousContextSide1, Muslim]
-
A.
religiousSide
chosen
Indicates that one entity is aligned with, belongs to, or represents a particular religious faction, denomination, or side in a religious context.
-
B.
religiousCounterpart
Indicates that one entity serves as the religious equivalent or analogue of another entity within a different belief system or tradition.
-
C.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
D.
religiousTopicAddressed
Indicates that a subject deals with, discusses, or focuses on a religious theme, issue, or question.
-
E.
originReligionContext
Indicates the religious background or setting from which something or someone originates or is derived.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 28, 2026, 7:48 p.m.