Triple
T31529018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dar Baachtar |
E804425
|
entity |
| Predicate | adminUnitLevel1 |
P87046
|
FINISHED |
| Object | North Governorate |
—
|
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: North Governorate | Statement: [Dar Baachtar, adminUnitLevel1, North Governorate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminUnitLevel1 Context triple: [Dar Baachtar, adminUnitLevel1, North Governorate]
-
A.
administrativeUnitLevel
chosen
Indicates the hierarchical level or rank of an administrative unit within an overall administrative or governmental structure.
-
B.
primaryLevelOfAdministration
Indicates that an entity functions as the main or highest-level administrative authority or division within a given territorial or organizational hierarchy.
-
C.
humanAccessLevel
Indicates the level or degree of access or permissions granted to a human within a system or context.
-
D.
authorizedUnit
Indicates that one entity is officially permitted or empowered to act on behalf of, or perform certain actions for, another entity or system.
-
E.
adminStatus
Indicates that an entity holds an administrative role, privilege level, or state within a system or context.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 30, 2026, 10 p.m.