Triple
T7680906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namdapha National Park |
E173989
|
entity |
| Predicate | declaredNationalPark |
P38404
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Namdapha National Park, declaredNationalPark, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredNationalPark Context triple: [Namdapha National Park, declaredNationalPark, 1983]
-
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.
nationalParkName
Indicates the name assigned to a national park.
-
D.
hasNationalParkSite
Indicates that a location, region, or jurisdiction contains or is home to at least one designated national park site.
-
E.
establishedAsNationalParkBy
Indicates that an area or site was officially designated and created as a national park through the action or authority of a specific person, organization, or governmental body.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.