Triple
T34629463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of al-Mahdi |
E889229
|
entity |
| Predicate | courtHead |
P76476
|
FINISHED |
| Object | al-Mahdi |
—
|
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: al-Mahdi | Statement: [court of al-Mahdi, courtHead, al-Mahdi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtHead Context triple: [court of al-Mahdi, courtHead, al-Mahdi]
-
A.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
-
B.
courtHeld
Indicates that a court has formally decided, ruled, or determined a particular legal issue or question.
-
C.
judicialHead
chosen
Indicates that one entity serves as the chief or leading judicial authority over another entity, such as a court or legal body.
-
D.
courtFeatured
Indicates that a particular court prominently presented, highlighted, or showcased a given entity (such as a case, event, or person) in an official or notable context.
-
E.
courtOfficial
Indicates that an entity serves in an official capacity within a court, holding an authorized role in judicial or legal proceedings.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.