Triple
T16703005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozilla VPN |
E405894
|
entity |
| Predicate | hasServerLocations |
P77880
|
FINISHED |
| Object | multiple geographic regions |
—
|
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 geographic regions | Statement: [Mozilla VPN, hasServerLocations, multiple geographic regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServerLocations Context triple: [Mozilla VPN, hasServerLocations, multiple geographic regions]
-
A.
hasServer
Indicates that one entity functions as or possesses a server that provides services or resources to another entity.
-
B.
hasChainLocations
chosen
Indicates that an entity operates or is associated with multiple locations belonging to the same chain or network.
-
C.
hasServerComponent
Indicates that an entity includes, depends on, or is associated with a particular server-side component.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
hasFacilityLocation
Indicates that an entity possesses or is associated with a facility situated at a specific location.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38333a6908190a17d2dee2ca622d6 |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.