Triple
T26222211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Investors Compensation Scheme Ltd v West Bromwich Building Society |
E655792
|
entity |
| Predicate | decisionDateApprox |
P877
|
FINISHED |
| Object | June 1997 |
—
|
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: June 1997 | Statement: [Investors Compensation Scheme Ltd v West Bromwich Building Society, decisionDateApprox, June 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionDateApprox Context triple: [Investors Compensation Scheme Ltd v West Bromwich Building Society, decisionDateApprox, June 1997]
-
A.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
-
B.
appealDate
Indicates the date on which an appeal is formally filed, recorded, or scheduled in relation to a decision or case.
-
C.
dismissalDate
Indicates the date on which an entity (such as a person, case, or employment) is formally dismissed, terminated, or ended.
-
D.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
E.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d5060708190b3134a5e5a4ca850 |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:56 p.m.