Triple
T20321254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | judicial branch of Syria |
E492210
|
entity |
| Predicate | recognizesReligiousCourtsFor |
P48958
|
FINISHED |
| Object | personal status matters |
—
|
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: personal status matters | Statement: [judicial branch of Syria, recognizesReligiousCourtsFor, personal status matters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesReligiousCourtsFor Context triple: [judicial branch of Syria, recognizesReligiousCourtsFor, personal status matters]
-
A.
recognizesCourt
chosen
Indicates that one legal authority formally accepts the legitimacy or jurisdiction of a particular court.
-
B.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
C.
religionOfCourt
Indicates the religious affiliation associated with a particular court.
-
D.
recognizesReligion
Indicates that one entity formally acknowledges or accepts another entity as a valid or legitimate religion.
-
E.
religiousLawView
Indicates a person's stance, interpretation, or opinion regarding a particular religious law or set of religious legal principles.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778b8b648190b80badaf15be2599 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.