Triple
T29725466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UKD74 |
E752167
|
entity |
| Predicate | replacedPreviousCodeSystem |
P68862
|
FINISHED |
| Object | UK pre‑NUTS local authority coding (functionally) |
—
|
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: UK pre‑NUTS local authority coding (functionally) | Statement: [UKD74, replacedPreviousCodeSystem, UK pre‑NUTS local authority coding (functionally)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedPreviousCodeSystem Context triple: [UKD74, replacedPreviousCodeSystem, UK pre‑NUTS local authority coding (functionally)]
-
A.
replacedCodeFor
Indicates that one code has been superseded or substituted by another code, typically in an updated or revised coding system.
-
B.
replacedSubsystem
Indicates that one subsystem has been substituted or exchanged for another, taking over its role or function.
-
C.
replacedEarlierSystems
chosen
Indicates that one system has taken the place of and superseded other systems that existed or were in use before it.
-
D.
replacedCode
Indicates that one piece of code has been substituted or superseded by another piece of code.
-
E.
UScodeDesignationReplacedBy
Indicates that one U.S. legal code designation has been superseded and replaced by another designation.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 28, 2026, 7:39 p.m.