Triple
T28739865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSICOP |
E730907
|
entity |
| Predicate | reportsAre |
P146555
|
FINISHED |
| Object | tabled in Parliament |
—
|
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: tabled in Parliament | Statement: [NSICOP, reportsAre, tabled in Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportsAre Context triple: [NSICOP, reportsAre, tabled in Parliament]
-
A.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
B.
reportsFor
Indicates that one entity is subordinate to another and is required to provide updates or answer to that entity, typically within an organizational or hierarchical structure.
-
C.
reportsAs
Indicates that one entity formally reports information, status, or results to another entity.
-
D.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
-
E.
reportsLaidBefore
chosen
Indicates that formal reports are presented or submitted to a designated authority or body for its consideration or record.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:02 a.m.