Triple
T3469584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Halton |
E73220
|
entity |
| Predicate | unitaryAuthoritySince |
P49152
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Borough of Halton, unitaryAuthoritySince, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitaryAuthoritySince Context triple: [Borough of Halton, unitaryAuthoritySince, 1998]
-
A.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
countySeatSince
Indicates that one place has served as the official county seat of a county starting from a specified point in time.
-
C.
governingSince
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
D.
governingBodyEstablished
Indicates that a particular governing body was formally created or brought into existence for an entity or domain.
-
E.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
- F. None of above. chosen
Provenance (4 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb392f6481908b6ad0457b8cf421 |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:17 p.m.