Triple
T14275649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communications Act 2003 |
E353908
|
entity |
| Predicate | part1Subject |
P450
|
FINISHED |
| Object | networks, services and the radio spectrum |
—
|
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: networks, services and the radio spectrum | Statement: [Communications Act 2003, part1Subject, networks, services and the radio spectrum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: part1Subject Context triple: [Communications Act 2003, part1Subject, networks, services and the radio spectrum]
-
A.
fourthPartSubject
Indicates that the subject is the fourth part or component within a larger ordered whole or sequence.
-
B.
secondPartSubject
Indicates that the referenced entity serves as the second part or component of the subject in a composite or multipart relationship.
-
C.
nameOfSubject
Indicates that the predicate specifies the name or label assigned to the subject entity.
-
D.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
E.
subjectMatter
chosen
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6583f0ec81909ebfc7a2c6351ff8 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.