Triple
T28739623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Momella Gate |
E730901
|
entity |
| Predicate | parkZonation |
P113031
|
FINISHED |
| Object | northern sector of Arusha National Park |
—
|
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: northern sector of Arusha National Park | Statement: [Momella Gate, parkZonation, northern sector of Arusha National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkZonation Context triple: [Momella Gate, parkZonation, northern sector of Arusha National Park]
-
A.
parkSection
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
-
B.
parkSystem
Indicates a relationship where an entity is part of, managed by, or associated with an organized system of parks or protected recreational areas.
-
C.
parkServed
Indicates that a particular park is provided with services or coverage by a specified entity (such as a transit line, facility, or administrative body).
-
D.
parkLocation
Indicates the place or area where something is parked or intended to be parked.
-
E.
zoningWithinPark
chosen
Indicates that a zoning area or designation lies entirely within the boundaries of a park.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657b2b1808190a9f7c80eef2efa99 |
completed | May 2, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6:02 a.m.