Triple
T7001196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet in Poland |
E162339
|
entity |
| Predicate | urbanCoverage |
P4903
|
FINISHED |
| Object | near universal |
—
|
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: near universal | Statement: [Internet in Poland, urbanCoverage, near universal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanCoverage Context triple: [Internet in Poland, urbanCoverage, near universal]
-
A.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
B.
dataCoverage
Indicates the extent or proportion of relevant data that is included, captured, or represented within a given dataset or system.
-
C.
coversCity
Indicates that one entity extends over, includes, or geographically encompasses the area of a specified city.
-
D.
cityWide
Indicates that something applies to, affects, or extends across an entire city.
-
E.
networkCoverage
chosen
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0f8830819091f4356296234713 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.