Triple
T32098894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karakhanid era |
E819791
|
entity |
| Predicate | hasPrevalentLaw |
P94537
|
FINISHED |
| Object | Islamic law |
—
|
NE NERFINISHED |
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 law | Statement: [Karakhanid era, hasPrevalentLaw, Islamic law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrevalentLaw Context triple: [Karakhanid era, hasPrevalentLaw, Islamic law]
-
A.
hasJurisprudence
Indicates a relationship where an entity possesses, is associated with, or is governed by a particular body of legal principles, case law, or judicial doctrine.
-
B.
haveLaw
chosen
Indicates that a governing body or jurisdiction possesses, enforces, or is characterized by a particular law or set of laws.
-
C.
containsLaw
Indicates that one entity (such as a document, code, or jurisdiction) includes or encompasses a specific law within it.
-
D.
stateOfLaw
Indicates that a specified legal condition, rule, or status is currently in force or applicable within a given jurisdiction or context.
-
E.
hasStatuteLaw
Indicates that a jurisdiction or entity is governed by, or possesses, a body of formal written laws enacted by a legislative authority.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: May 1, 2026, 12:26 a.m.