Triple
T8559261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad hoc committees (India) |
E202649
|
entity |
| Predicate | mayBeJointBetween |
P83620
|
FINISHED |
| Object | Lok Sabha and Rajya Sabha |
—
|
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: Lok Sabha and Rajya Sabha | Statement: [Ad hoc committees (India), mayBeJointBetween, Lok Sabha and Rajya Sabha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeJointBetween Context triple: [Ad hoc committees (India), mayBeJointBetween, Lok Sabha and Rajya Sabha]
-
A.
mayBeManagedJointlyWith
Indicates that an entity can be administered, controlled, or overseen together with another entity as part of a shared or coordinated management arrangement.
-
B.
hasJointType
Indicates that one entity is associated with, or characterized by, a specific type or category of joint.
-
C.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
D.
isJointPosition
Indicates that an entity occupies or specifies a particular position or configuration within a joint (e.g., in a mechanical, robotic, or anatomical system).
-
E.
hasJunctionIn
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe949974c8190a75d9c767ca5fa5a |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:20 p.m.