Triple
T21165181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelter Cove Road |
E521540
|
entity |
| Predicate | cellCoverage |
P4903
|
FINISHED |
| Object | spotty or limited |
—
|
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: spotty or limited | Statement: [Shelter Cove Road, cellCoverage, spotty or limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellCoverage Context triple: [Shelter Cove Road, cellCoverage, spotty or limited]
-
A.
networkCoverage
chosen
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
-
B.
dataCoverage
Indicates the extent or proportion of relevant data that is included, captured, or represented within a given dataset or system.
-
C.
hasAreaOfCoverage
Indicates that an entity provides services, influence, or applicability within a specified geographic or conceptual region.
-
D.
cellReselectionSupport
Indicates whether a network cell is configured to allow and support mobile devices moving their connection (reselecting) from one cell to another.
-
E.
cellularLocation
Indicates the location or compartment within a cell where an entity (such as a molecule or process) is situated or occurs.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7270e15bc81908d609198e573040e |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.