Triple
T9172162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eravikulam National Park |
E220105
|
entity |
| Predicate | endangeredSpecies |
P73394
|
FINISHED |
| Object | Nilgiri tahr |
—
|
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: Nilgiri tahr | Statement: [Eravikulam National Park, endangeredSpecies, Nilgiri tahr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endangeredSpecies Context triple: [Eravikulam National Park, endangeredSpecies, Nilgiri tahr]
-
A.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
B.
endangeredMembers
chosen
Indicates that the members of a group, category, or population are at risk of extinction or serious harm.
-
C.
areEndangeredInPart
Indicates that an entity is endangered only in certain regions or parts of its overall range, rather than throughout its entire distribution.
-
D.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
E.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbf9fe79c819082f335c2fdd1c7d3 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.