Triple
T22188087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fatimid state courts |
E548346
|
entity |
| Predicate | employedOfficial |
P8156
|
FINISHED |
| Object | qadi |
—
|
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: qadi | Statement: [Fatimid state courts, employedOfficial, qadi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedOfficial Context triple: [Fatimid state courts, employedOfficial, qadi]
-
A.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
B.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
C.
employedSystem
Indicates that a system is used or operated in the context of an employment or work-related arrangement.
-
D.
employedThrough
Indicates that an entity holds a job or work position by means of, or via the arrangement of, another entity (such as an agency, contractor, or intermediary).
-
E.
officialIn
chosen
Indicates that an entity holds an official position, role, or office within a specified organization, institution, or jurisdiction.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aaa32288190830f6dfc626fb26a |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.