Triple
T4582955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Widgery Tribunal |
E101896
|
entity |
| Predicate | investigatedDate |
P1160
|
FINISHED |
| Object | 30 January 1972 |
—
|
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: 30 January 1972 | Statement: [Widgery Tribunal, investigatedDate, 30 January 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigatedDate Context triple: [Widgery Tribunal, investigatedDate, 30 January 1972]
-
A.
allegedInvolvementDate
Indicates the date on which an entity is claimed or reported to have been involved in a particular event or activity, without asserting that the involvement is confirmed.
-
B.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
C.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
D.
dateObserved
chosen
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
E.
depositionDate
Indicates the date on which something (such as a document, sample, or record) was formally submitted, filed, or placed into a repository or system.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59029568819091db1e77a9a2ec41 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.