Triple
T31740710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shillong Lok Sabha constituency |
E810131
|
entity |
| Predicate | currentStateCapitalCovered |
P204
|
FINISHED |
| Object | Shillong |
—
|
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: Shillong | Statement: [Shillong Lok Sabha constituency, currentStateCapitalCovered, Shillong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentStateCapitalCovered Context triple: [Shillong Lok Sabha constituency, currentStateCapitalCovered, Shillong]
-
A.
coversCapital
Indicates that one entity provides coverage, service, or applicability specifically to the capital city of another entity.
-
B.
sectorCapitalOf
Indicates that one entity serves as the capital or primary administrative center of a specified sector or regional division.
-
C.
accessStateCapital
Indicates that an entity has the ability or permission to reach, use, or interact with the capital city of a given state.
-
D.
regionCapitalStatus
Indicates that one entity serves as the capital of a specified region or administrative area in relation to another entity.
-
E.
hasCapital
chosen
Indicates that a place or political entity has a specific city designated as its capital.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: April 30, 2026, 11:24 p.m.