Triple
T8559269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad hoc committees (India) |
E202649
|
entity |
| Predicate | canExamine |
P8869
|
FINISHED |
| Object | legislative proposals |
—
|
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: legislative proposals | Statement: [Ad hoc committees (India), canExamine, legislative proposals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canExamine Context triple: [Ad hoc committees (India), canExamine, legislative proposals]
-
A.
canExhibit
Indicates that one entity has the ability or potential to display, manifest, or show a particular property, behavior, or characteristic.
-
B.
canReview
chosen
Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
-
C.
canAccedeTo
Indicates that one entity has the ability, permission, or right to gain access to or enter into another entity, resource, or state.
-
D.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
-
E.
canSupervise
Indicates that one entity has the authority or capability to oversee, direct, or manage the work or activities of another entity.
- 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_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. |
Created at: March 30, 2026, 6:20 p.m.