Triple
T632752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freesat |
E15956
|
entity |
| Predicate | signalCoverage |
P4903
|
FINISHED |
| Object | via satellite footprint over UK |
—
|
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: via satellite footprint over UK | Statement: [Freesat, signalCoverage, via satellite footprint over UK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalCoverage Context triple: [Freesat, signalCoverage, via satellite footprint over UK]
-
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.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
C.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
D.
fieldCovered
Indicates that a specified field or area is physically or functionally covered by some material, object, or condition.
-
E.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec2a4c08190bc5c6ce8a10b0967 |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.