Triple
T27753123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serengeti wildebeest migration |
E701262
|
entity |
| Predicate | distancePerYear |
P16230
|
FINISHED |
| Object | approximately 800 to 1,000 kilometers |
—
|
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: approximately 800 to 1,000 kilometers | Statement: [Serengeti wildebeest migration, distancePerYear, approximately 800 to 1,000 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distancePerYear Context triple: [Serengeti wildebeest migration, distancePerYear, approximately 800 to 1,000 kilometers]
-
A.
distanceTraveled
chosen
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
B.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
distanceProvidedBy
Indicates that a specific distance value is supplied or made available by a particular source or provider.
-
D.
scheduledDistanceMi
Indicates the planned or expected distance in miles associated with a scheduled event or activity.
-
E.
distanceChange
Indicates a change in the spatial distance between two entities over time.
- 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_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: April 27, 2026, 4:21 p.m.