Triple
T25787574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhyiddin |
E649460
|
entity |
| Predicate | bearerSchoolOfLaw |
P78579
|
FINISHED |
| Object | Shafi'i |
—
|
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: Shafi'i | Statement: [Muhyiddin, bearerSchoolOfLaw, Shafi'i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerSchoolOfLaw Context triple: [Muhyiddin, bearerSchoolOfLaw, Shafi'i]
-
A.
associatedSchoolOfLaw
Indicates a relationship where an entity is connected or linked to a particular school of law, typically as its legal education institution or legal academic affiliation.
-
B.
lawSchoolName
Indicates the name of the law school with which an entity (such as a person or institution) is associated.
-
C.
majorSchoolOfLaw
Indicates that a particular school of law is a primary or dominant legal tradition or framework associated with an entity.
-
D.
legalSchoolFoundedIn
Indicates that a law school was established or came into existence in a specific year or time period.
-
E.
schoolOfJurisprudence
chosen
Indicates that one entity is a legal philosophy, doctrine, or interpretive framework to which the other entity (such as a jurist, decision, or institution) adheres or belongs.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 5:56 a.m.