Triple
T35392807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jahanabad Lok Sabha constituency |
E1022985
|
entity |
| Predicate | assemblySegmentsType |
P63908
|
FINISHED |
| Object | Vidhan Sabha segments |
—
|
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: Vidhan Sabha segments | Statement: [Jahanabad Lok Sabha constituency, assemblySegmentsType, Vidhan Sabha segments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblySegmentsType Context triple: [Jahanabad Lok Sabha constituency, assemblySegmentsType, Vidhan Sabha segments]
-
A.
assemblySegments
chosen
Indicates that an entity is composed of or associated with specific component segments that together form its assembly.
-
B.
assemblySegmentsState
Indicates the condition or status of the individual segments that make up an assembly.
-
C.
hasAssemblySegment
Indicates that an object or system includes a specific segment as part of its overall assembly structure.
-
D.
issAssemblySequence
Indicates that one entity specifies the ordered sequence of assembly steps or components required to construct another entity.
-
E.
assemblyLinkedTo
Indicates that one assembly is associated or connected to another assembly in a meaningful or functionally relevant way.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794fd5fd08190ab39a0c8882536df |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.