Triple
T32024071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Member of Parliament, Lok Sabha |
E817770
|
entity |
| Predicate | canBeDissolvedWithHouse |
P195317
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Member of Parliament, Lok Sabha, canBeDissolvedWithHouse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDissolvedWithHouse Context triple: [Member of Parliament, Lok Sabha, canBeDissolvedWithHouse, yes]
-
A.
canBeDissolvedWhen
Indicates that one substance is capable of dissolving under the specific conditions, time, or circumstances denoted by the related entity or event.
-
B.
canBeDissolvedWith
Indicates that one entity is capable of being dissolved or broken down when exposed to another specified substance or medium.
-
C.
canDissolveWith
Indicates that one substance is capable of dissolving another substance when they are combined.
-
D.
mayBeDissolvedBy
Indicates that one entity has the potential or capability to dissolve another entity.
-
E.
canBeDissolvedEarly
Indicates that the agreement, contract, or arrangement is allowed to be terminated before its originally specified end date.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
| PDg | Predicate description generation | batch_69fdbaa1313081908beea28a5597ae40 |
completed | May 8, 2026, 10:27 a.m. |
Created at: May 1, 2026, 12:17 a.m.