Triple
T4513480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Venkateswara National Park |
E102102
|
entity |
| Predicate | notifiedAsNationalPark |
P38404
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Sri Venkateswara National Park, notifiedAsNationalPark, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notifiedAsNationalPark Context triple: [Sri Venkateswara National Park, notifiedAsNationalPark, 1998]
-
A.
designatedAsNationalPark
chosen
Indicates that an area has been officially assigned the legal status and protections of a national park by an authorized governing body.
-
B.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
C.
hasNationalParkSite
Indicates that a location, region, or jurisdiction contains or is home to at least one designated national park site.
-
D.
withinNationalPark
Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
-
E.
hasNationalParkServicePresence
Indicates that the National Park Service operates, manages, or maintains an official presence at the referenced location or entity.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5722d8fc81909c5f2d9a38d17a6b |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.