Triple
T288086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Leopold |
E5928
|
entity |
| Predicate | hasReligiousNeutrality |
P7601
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Order of Leopold, hasReligiousNeutrality, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousNeutrality Context triple: [Order of Leopold, hasReligiousNeutrality, yes]
-
A.
religionPolicy
chosen
Indicates the stance, rules, or approach an entity adopts toward religious beliefs, practices, or institutions.
-
B.
dominantReligionPolicy
Indicates the policy or stance an authority adopts toward the religion that holds dominant or majority status within a given context.
-
C.
legalStatusOfReligion
Indicates the formal legal standing, recognition, and regulatory conditions of a religion within a given jurisdiction or political entity.
-
D.
officialReligion
Indicates that a particular religion is formally recognized and designated as the official or state religion of an entity (such as a country or region).
-
E.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2f5c0081908e548b314f5e986d |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7c1448819082064f474633acd5 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.