Triple
T8559449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estimates Committee (India) |
E202653
|
entity |
| Predicate | reportsType |
P20605
|
FINISHED |
| Object | recommendatory reports |
—
|
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: recommendatory reports | Statement: [Estimates Committee (India), reportsType, recommendatory reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportsType Context triple: [Estimates Committee (India), reportsType, recommendatory reports]
-
A.
reportType
chosen
Indicates the specific category or kind of report associated with an entity or action.
-
B.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
C.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
-
D.
reportsImplementedBy
Indicates that a report is realized, produced, or carried out by a specific implementing entity or system.
-
E.
reportsInStandard
Indicates that something is reported or presented according to a specified standard or standardized format.
- 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.