Triple
T18060958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice and Security Act 2013 |
E432170
|
entity |
| Predicate | gaveISCStatus |
P129667
|
FINISHED |
| Object | committee of 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: committee of Parliament | Statement: [Justice and Security Act 2013, gaveISCStatus, committee of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaveISCStatus Context triple: [Justice and Security Act 2013, gaveISCStatus, committee of Parliament]
-
A.
grantedStatus
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
B.
hasNationalStatus
Indicates that an entity possesses an official national-level designation, recognition, or status within a country.
-
C.
hasISWCStatus
Indicates that an entity has a specific ISWC (International Standard Musical Work Code) status assigned or associated with it.
-
D.
isoClassificationStatus
Indicates the current status or stage of an entity within an ISO-based classification or standardization process.
-
E.
governsStatusOf
Indicates that one entity has authority or control over determining or regulating the status or condition 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c1066f508190bacf1122e366f87b |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:26 a.m.