Triple
T21418035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nandom |
E528356
|
entity |
| Predicate | hasBasicServices |
P143887
|
FINISHED |
| Object | primary schools |
—
|
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: primary schools | Statement: [Nandom, hasBasicServices, primary schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasicServices Context triple: [Nandom, hasBasicServices, primary schools]
-
A.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
B.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
D.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
E.
hasBasicUnit
Indicates that one entity is composed of, defined by, or fundamentally characterized through another entity that serves as its basic or minimal unit.
- F. None of above. chosen
Provenance (4 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee62d29f948190b820c92014d1c53a |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:46 p.m.