Triple
T4913073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panna National Park |
E110280
|
entity |
| Predicate | tigerReserveNotificationYear |
P40335
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Panna National Park, tigerReserveNotificationYear, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tigerReserveNotificationYear Context triple: [Panna National Park, tigerReserveNotificationYear, 1994]
-
A.
designatedAsTigerReserve
chosen
Indicates that an area has been officially declared and assigned the status of a tiger reserve for the purpose of tiger conservation.
-
B.
iucnAssessmentYear
Indicates the year in which the IUCN conservation status assessment for an entity was conducted or published.
-
C.
wildlifeProtectionStatus
Indicates the level or type of legal or conservation protection currently applied to wildlife.
-
D.
natureReserveSince
Indicates that an area has held the legal or official status of a nature reserve since a specified point in time.
-
E.
expansionAnnouncementYear
Indicates the year in which an expansion (such as a project, product, or service extension) was officially announced.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9dc41481908c0c398852e6819c |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.