Triple
T33022509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marayoor |
E844949
|
entity |
| Predicate | hasForestDepartmentFacility |
P194566
|
FINISHED |
| Object | sandalwood depot |
—
|
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: sandalwood depot | Statement: [Marayoor, hasForestDepartmentFacility, sandalwood depot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForestDepartmentFacility Context triple: [Marayoor, hasForestDepartmentFacility, sandalwood depot]
-
A.
hasForestDivisionOffice
Indicates that an entity maintains or is associated with a specific forest division office as part of its organizational or administrative structure.
-
B.
forestDistrict
Indicates that one entity functions as the forest district or forest management administrative unit responsible for the other entity.
-
C.
hasNationalForest
Indicates that a place or jurisdiction contains, includes, or is home to at least one designated national forest.
-
D.
hasForestType
Indicates that an area or location is characterized by a specific type or classification of forest.
-
E.
hasAccessToForestResources
Indicates that one entity is permitted or able to use, enter, or benefit from forest resources controlled by another entity.
- F. None of above. chosen
Provenance (4 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fd7b042a548190b3abe31bc3258278 |
completed | May 8, 2026, 5:56 a.m. |
Created at: May 1, 2026, 1:23 a.m.