Triple
T33022498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marayoor |
E844949
|
entity |
| Predicate | locatedInTaluk |
P197074
|
FINISHED |
| Object | Devikulam taluk |
E679982
|
NE 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: Devikulam taluk | Statement: [Marayoor, locatedInTaluk, Devikulam taluk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTaluk Context triple: [Marayoor, locatedInTaluk, Devikulam taluk]
-
A.
hasTehsil
Indicates a relationship where an administrative region or district includes or is associated with a specific tehsil (sub-district) within its jurisdiction.
-
B.
locatedInUnionTerritory
Indicates that an entity is geographically situated within a specified union territory.
-
C.
administrativeTaluka
chosen
Indicates that one entity serves as the administrative taluka (sub-district level administrative unit) governing or associated with another entity.
-
D.
locatedInLocalGovernmentUnit
Indicates that one entity is geographically or administratively situated within the boundaries of a specific local government unit.
-
E.
locatedNearGovernmentDistrict
Indicates that one entity is situated close to or in the immediate vicinity of a government district.
- F. None of above.
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_6a035052a47081908e9e56e21c543d46 |
completed | May 12, 2026, 4:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34dadd1380819087d651f08dc94e5e |
completed | June 19, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a034d306e588190a2dce906fd46eb54 |
completed | May 12, 2026, 3:54 p.m. |
Created at: May 1, 2026, 1:23 a.m.