Triple
T11725797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajbagh Talao |
E278762
|
entity |
| Predicate | parkZone |
P5641
|
FINISHED |
| Object | core area of Ranthambore National Park |
—
|
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: core area of Ranthambore National Park | Statement: [Rajbagh Talao, parkZone, core area of Ranthambore National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkZone Context triple: [Rajbagh Talao, parkZone, core area of Ranthambore National Park]
-
A.
parkSection
chosen
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
-
B.
parkArea
Indicates that an area of land is designated and used as a park or recreational green space.
-
C.
parkServed
Indicates that a particular park is provided with services or coverage by a specified entity (such as a transit line, facility, or administrative body).
-
D.
parkType
Indicates the specific category or classification of a park based on its designated use, management, or characteristics.
-
E.
parkSystem
Indicates a relationship where an entity is part of, managed by, or associated with an organized system of parks or protected recreational areas.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d70d908190b5f47c2ef501a191 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.