Triple
T16680296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Nakuru |
E405320
|
entity |
| Predicate | withinNationalParkSince |
P54654
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Lake Nakuru, withinNationalParkSince, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinNationalParkSince Context triple: [Lake Nakuru, withinNationalParkSince, 1968]
-
A.
withinNationalPark
Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
-
B.
servedNationalPark
Indicates that an entity has provided official service or worked in an official capacity for a national park.
-
C.
associatedWithNationalPark
Indicates a relationship in which an entity has a connection or linkage to a specific national park, such as location, administration, or relevant activity.
-
D.
establishedAsPark
chosen
Indicates that an area or site has been officially designated and recognized as a park.
-
E.
locatedInNationalOrProvincialPark
Indicates that one entity is situated within the boundaries of a national or provincial 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d6e74ec81909ea95c3e4b0113ab |
completed | April 18, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.