Triple
T29483446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umm al-Ghanam |
E747854
|
entity |
| Predicate | formsLocalCouncilWith |
P39103
|
FINISHED |
| Object | Shibli |
—
|
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: Shibli | Statement: [Umm al-Ghanam, formsLocalCouncilWith, Shibli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsLocalCouncilWith Context triple: [Umm al-Ghanam, formsLocalCouncilWith, Shibli]
-
A.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
-
B.
formsLocalityWith
chosen
Indicates that two or more entities together constitute or define a specific locality or local area.
-
C.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
-
D.
formedMunicipalityWith
Indicates that two or more entities combined or were merged to create a single municipality.
-
E.
mayorCouncilForm
Indicates that a municipality operates under a mayor–council form of government, where executive authority is vested in an elected mayor and legislative authority in an elected council.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 4:06 p.m.