Triple
T35075529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross River gorilla |
E1011999
|
entity |
| Predicate | countryOfConservationAction |
P197924
|
FINISHED |
| Object | Nigeria |
E2050
|
NE 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: Nigeria | Statement: [Cross River gorilla, countryOfConservationAction, Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfConservationAction Context triple: [Cross River gorilla, countryOfConservationAction, Nigeria]
-
A.
countryOfConservationProgram
chosen
Indicates the country in which a given conservation program is implemented or officially associated.
-
B.
countryOfProtectedArea
Indicates that a protected natural area is located within and legally belongs to a specific country.
-
C.
conservationListedBy
Indicates that an entity is recognized or recorded as a conservation concern by a specific authority, organization, or listing body.
-
D.
conservationActions
Indicates actions or measures undertaken to protect, restore, or sustainably manage a species, habitat, or ecosystem.
-
E.
typeOfConservation
Indicates the specific kind or category of conservation practice, method, or approach that applies to an entity or situation.
- F. None of above.
Provenance (4 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01a23d8b148190ac2c8765aa9227c4 |
completed | May 11, 2026, 9:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cfd9ea808190ad828b8dddbba8f8 |
completed | June 21, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_6a01a1e8bb90819096647e929bfb3db8 |
completed | May 11, 2026, 9:31 a.m. |
Created at: May 3, 2026, 4:01 p.m.