Triple
T27753124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serengeti wildebeest migration |
E701262
|
entity |
| Predicate | peakCalvingLocation |
P14801
|
FINISHED |
| Object | southern Serengeti |
—
|
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: southern Serengeti | Statement: [Serengeti wildebeest migration, peakCalvingLocation, southern Serengeti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakCalvingLocation Context triple: [Serengeti wildebeest migration, peakCalvingLocation, southern Serengeti]
-
A.
calvingGrounds
chosen
Indicates areas where animals, typically large mammals, go to give birth and rear their newborns.
-
B.
glaciologicalRegion
Indicates the geographic area or zone defined and studied in relation to glaciers and glacial processes.
-
C.
notableGlacier
Indicates that the subject is a glacier recognized for its particular significance, prominence, or noteworthiness.
-
D.
liesNearGlacier
Indicates that one entity is located in close physical proximity to a glacier.
-
E.
glaciationCenter
Indicates the location that serves as the primary source or focal point from which glaciation originates or is organized.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6375ece288190bec1ca486bbd2f12 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:21 p.m.