Triple
T32839575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puducherry (Lok Sabha constituency) |
E839924
|
entity |
| Predicate | includesEnclave |
P3946
|
FINISHED |
| Object | Mahe |
E274360
|
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: Mahe | Statement: [Puducherry (Lok Sabha constituency), includesEnclave, Mahe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEnclave Context triple: [Puducherry (Lok Sabha constituency), includesEnclave, Mahe]
-
A.
containsEnclave
chosen
Indicates that one region or territory fully surrounds and encloses another distinct region or territory as an enclave.
-
B.
isCivilEnclave
Indicates that a location or facility is a civilian enclave situated within or using a military airfield or installation.
-
C.
typeOfEnclave
Indicates that one entity is an enclave and specifies the kind or category of enclave it is (e.g., political, cultural, economic).
-
D.
hasExclave
Indicates that a territory or administrative unit possesses an exclave—part of its area that is geographically separated from its main portion and surrounded by foreign territory.
-
E.
borderIncludesEnclaveRegion
Indicates that a border surrounds or contains an enclave region within its boundaries.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34effbe60481908b98b1e5001ed3e0 |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
Created at: May 1, 2026, 1:16 a.m.