Triple
T37633215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periyar |
E936410
|
entity |
| Predicate | protectedAreaAssociated |
P86799
|
FINISHED |
| Object | Periyar Tiger Reserve |
—
|
NE NERFINISHED |
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: Periyar Tiger Reserve | Statement: [Periyar, protectedAreaAssociated, Periyar Tiger Reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedAreaAssociated Context triple: [Periyar, protectedAreaAssociated, Periyar Tiger Reserve]
-
A.
protectedAreaAssociation
chosen
Indicates an association where one entity is designated as, or linked to, a protected area in relation to another entity.
-
B.
protectedAreaName
Indicates the designated name assigned to a protected area.
-
C.
protectedAreaGateway
Indicates that an entity serves as an entrance or access point leading into a protected or restricted area.
-
D.
protectedAreaEstablishedBy
Indicates that a protected area was formally created, designated, or brought into legal existence by a specific agent or authority.
-
E.
protectedAreaCountry
Indicates that a protected area is located within and legally falls under the jurisdiction of a specific country.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.