Triple
T1473331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hijra |
E27184
|
entity |
| Predicate | legalSignificanceIn |
P12084
|
FINISHED |
| Object | Islamic jurisprudence |
—
|
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: Islamic jurisprudence | Statement: [Hijra, legalSignificanceIn, Islamic jurisprudence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalSignificanceIn Context triple: [Hijra, legalSignificanceIn, Islamic jurisprudence]
-
A.
legalSignificance
chosen
Indicates that something has recognized importance, effect, or consequence within a legal context or system.
-
B.
legalContext
Indicates that the relationship or action occurs within, is shaped by, or is relevant to a specific legal framework, proceeding, or set of legal norms.
-
C.
legalConcept
Indicates a relationship where something is classified or treated as a concept defined and governed by law or legal theory.
-
D.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
E.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.