Triple
T37567400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahe railway station |
E933994
|
entity |
| Predicate | servesStateBorderArea |
P201461
|
FINISHED |
| Object | Kerala–Puducherry (Mahe enclave) |
—
|
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: Kerala–Puducherry (Mahe enclave) | Statement: [Mahe railway station, servesStateBorderArea, Kerala–Puducherry (Mahe enclave)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesStateBorderArea Context triple: [Mahe railway station, servesStateBorderArea, Kerala–Puducherry (Mahe enclave)]
-
A.
servesBorder
Indicates that one entity functions as a boundary or border for another entity.
-
B.
stateBorderContext
Indicates that one state shares a border with another state within a specified geographic or political context.
-
C.
servesCrossBorderArea
Indicates that a service, activity, or function extends beyond a single jurisdiction and operates across national or regional borders.
-
D.
borderDistrictState
Indicates that a district shares a common boundary with a state.
-
E.
borderTownServed
chosen
Indicates that a town located near a border is provided with services or support by a specified entity.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
Created at: May 3, 2026, 4:17 p.m.