Triple
T37405763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skipton Rural District Council (part) |
E929124
|
entity |
| Predicate | absorbedIntoUnderAct |
P188036
|
FINISHED |
| Object | Local Government Act 1972 |
—
|
NE NERFINISHED |
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: Local Government Act 1972 | Statement: [Skipton Rural District Council (part), absorbedIntoUnderAct, Local Government Act 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: absorbedIntoUnderAct Context triple: [Skipton Rural District Council (part), absorbedIntoUnderAct, Local Government Act 1972]
-
A.
madeUnderAct
Indicates that something was created, established, or carried out in accordance with a specific legal act or statute.
-
B.
absorbed
Indicates that one entity takes in, soaks up, or assimilates another entity or substance.
-
C.
actedUnderAuthorityOf
Indicates that one entity performed actions under the direction, control, or legal authority of another entity.
-
D.
absorbedIntoOnEvent
chosen
Indicates that one entity becomes incorporated into or merged with another entity as a result of a specific event.
-
E.
laterUnderRuleOf
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.