Triple
T29837120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaikom |
E757684
|
entity |
| Predicate | isTalukHeadquartersOf |
P139183
|
FINISHED |
| Object | Vaikom taluk |
—
|
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: Vaikom taluk | Statement: [Vaikom, isTalukHeadquartersOf, Vaikom taluk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTalukHeadquartersOf Context triple: [Vaikom, isTalukHeadquartersOf, Vaikom taluk]
-
A.
isTehsilHeadquarters
chosen
Indicates that a location serves as the administrative headquarters for a tehsil (sub-district) within an administrative division.
-
B.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
C.
hasTehsil
Indicates a relationship where an administrative region or district includes or is associated with a specific tehsil (sub-district) within its jurisdiction.
-
D.
mandalHeadquartersOf
Indicates that a location serves as the administrative headquarters for a specified mandal (sub-district).
-
E.
hasCouncilAreaName
Indicates that an entity is associated with a council area identified by a specific name.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760709588190affa39e86d0322f0 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:37 p.m.