Triple
T14671086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cookson’s wildebeest |
E344512
|
entity |
| Predicate | hasLocallySmallPopulation |
P109384
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cookson’s wildebeest, hasLocallySmallPopulation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocallySmallPopulation Context triple: [Cookson’s wildebeest, hasLocallySmallPopulation, true]
-
A.
hasVerySmallResidentPopulation
Indicates that the subject location has a resident population that is extremely small in size.
-
B.
hasSmallCommunities
chosen
Indicates that an entity possesses or is characterized by the presence of relatively small communities within it.
-
C.
hasLowPopulationDensity
Indicates that the number of individuals or entities per unit area in a given region is relatively small compared to typical or expected levels.
-
D.
populationThreshold
Indicates that a population has reached, exceeded, or fallen below a specified numerical limit used as a critical or decision-making boundary.
-
E.
hasNotablePopulation
Indicates that an entity is recognized for having a significant or noteworthy number of inhabitants or members.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54ef2908190b189ced65eec434a |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.