Triple
T10682752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham PlusBus area |
E251796
|
entity |
| Predicate | operatorCoverageIncludes |
P42076
|
FINISHED |
| Object | multiple local bus operators |
—
|
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: multiple local bus operators | Statement: [Nottingham PlusBus area, operatorCoverageIncludes, multiple local bus operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorCoverageIncludes Context triple: [Nottingham PlusBus area, operatorCoverageIncludes, multiple local bus operators]
-
A.
componentCoverage
Indicates that one entity provides coverage, protection, or support for another as one of its components or constituent parts.
-
B.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
C.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
D.
hasCoverageFocus
Indicates that one entity’s coverage, attention, or analysis is specifically focused on or directed toward another entity.
-
E.
providesCoverage
chosen
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc43b9481908f35490db93db76c |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.