Triple
T11747829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BST Act 1972 |
E279328
|
entity |
| Predicate | startTimeRule |
P67082
|
FINISHED |
| Object | BST begins in spring |
—
|
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: BST begins in spring | Statement: [BST Act 1972, startTimeRule, BST begins in spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeRule Context triple: [BST Act 1972, startTimeRule, BST begins in spring]
-
A.
requiresStartTime
Indicates that an entity cannot be valid, initiated, or executed unless a specific start time has been provided or is in effect.
-
B.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
C.
usesTimingRules
chosen
Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
-
D.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
-
E.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50763a081908597da118bd0a64e |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.