Triple
T34687429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahir ibn al-Husayn |
E890789
|
entity |
| Predicate | governorateStart |
P25420
|
FINISHED |
| Object | 821 |
—
|
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: 821 | Statement: [Tahir ibn al-Husayn, governorateStart, 821]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governorateStart Context triple: [Tahir ibn al-Husayn, governorateStart, 821]
-
A.
governorateEstablished
Indicates that a particular governorate (administrative region) was formally created or brought into official existence at a certain time or by a specific act.
-
B.
termStartAsGovernor
chosen
Indicates the date or point in time when an individual begins their term serving in the role of governor.
-
C.
currentGovernorStartDate
Indicates the date on which the entity’s current governorship officially began.
-
D.
governorateSystem
Indicates a system in which a territory or region is organized, administered, or governed as a governorate.
-
E.
assumedOfficeAsGovernor
Indicates that an individual formally took on and began serving in the role of governor of a specific 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: May 1, 2026, 2:05 a.m.