Triple
T27912990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balurghat (Lok Sabha constituency) |
E705985
|
entity |
| Predicate | assemblySegmentsState |
P164365
|
FINISHED |
| Object | West Bengal |
—
|
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: West Bengal | Statement: [Balurghat (Lok Sabha constituency), assemblySegmentsState, West Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblySegmentsState Context triple: [Balurghat (Lok Sabha constituency), assemblySegmentsState, West Bengal]
-
A.
assemblySegments
Indicates that an entity is composed of or associated with specific component segments that together form its assembly.
-
B.
assemblyState
Indicates the current configuration or completeness status of an object or system in its assembly process.
-
C.
assemblyStatus
Indicates the current stage or condition of an item or system in its assembly process.
-
D.
hasAssemblySegment
Indicates that an object or system includes a specific segment as part of its overall assembly structure.
-
E.
assemblyLinkedTo
Indicates that one assembly is associated or connected to another assembly in a meaningful or functionally relevant way.
- F. None of above. chosen
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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 6:51 p.m.