Triple
T31529017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dar Baachtar |
E804425
|
entity |
| Predicate | adminUnitLevel2 |
P87046
|
FINISHED |
| Object | Koura District |
—
|
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: Koura District | Statement: [Dar Baachtar, adminUnitLevel2, Koura District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminUnitLevel2 Context triple: [Dar Baachtar, adminUnitLevel2, Koura District]
-
A.
administrativeUnitLevel
chosen
Indicates the hierarchical level or rank of an administrative unit within an overall administrative or governmental structure.
-
B.
hasAdministrativeUnit
Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
-
C.
roleInAdministration
Indicates that an entity holds a specific position or function within an administrative structure or governing body.
-
D.
humanAccessLevel
Indicates the level or degree of access or permissions granted to a human within a system or context.
-
E.
dualAdministration
Indicates that authority or management over something is shared or exercised jointly by two distinct administrative bodies or systems.
- 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 30, 2026, 10 p.m.