Triple
T28470671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Mithnab |
E720426
|
entity |
| Predicate | isPopulatedLocalityOf |
P45808
|
FINISHED |
| Object | Qassim Region |
—
|
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: Qassim Region | Statement: [Al Mithnab, isPopulatedLocalityOf, Qassim Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopulatedLocalityOf Context triple: [Al Mithnab, isPopulatedLocalityOf, Qassim Region]
-
A.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
B.
hasLocalities
Indicates that an entity is associated with, contains, or is linked to one or more specific geographic or administrative local areas.
-
C.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
isPopulatedPlace
chosen
Indicates that the subject is a geographic location where people live or have lived, such as a city, town, village, or settlement.
-
E.
hasUrbanLocalities
Indicates that an entity possesses or includes one or more urban localities within its jurisdiction or scope.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64ee1c4d08190ba95b02f3aa0ca67 |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:48 a.m.