Triple
T5850840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusader military orders |
E130025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious-military order |
C18994
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: religious-military order Context triple: [Crusader military orders, instanceOf, religious-military order]
-
A.
religious order presence
The "religious order presence" class represents the existence, extent, and characteristics of one or more organized religious communities or orders within a given context, such as a location, institution, or time period.
-
B.
male religious order
A male religious order is an organized community of men who live under shared spiritual rules and vows, dedicated to religious service, prayer, and often charitable or educational work.
-
C.
Catholic religious order
A Catholic religious order is a community of men or women in the Catholic Church who profess public vows and live a shared spiritual, communal, and often apostolic life according to a specific rule and charism.
-
D.
military ordinariate
A military ordinariate is a specific ecclesiastical jurisdiction of the Catholic Church that provides pastoral care and spiritual services to members of the armed forces and their families, often across multiple dioceses or national boundaries.
-
E.
Islamic religious order
An Islamic religious order is an organized community within Islam, often centered around a spiritual lineage, shared rituals, and teachings, that guides its members in religious practice, moral conduct, and devotion to God.
- F. None of above. chosen
Provenance (1 batch)
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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:55 p.m.