Triple
T36584724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Education Act 1964 (remaining provisions) |
E902490
|
entity |
| Predicate | statusInForce |
P19388
|
FINISHED |
| Object | partially repealed |
—
|
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: partially repealed | Statement: [Education Act 1964 (remaining provisions), statusInForce, partially repealed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInForce Context triple: [Education Act 1964 (remaining provisions), statusInForce, partially repealed]
-
A.
inForceStatus
chosen
Indicates that a rule, agreement, or condition is currently active, valid, and legally or formally in effect.
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
statusInRFCIndex
Indicates that an item has a particular status as recorded in the RFC index.
-
E.
statusBasis
Indicates the underlying reason, condition, or justification on which a particular status or state is based.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.