Triple
T28628016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia servers |
E724571
|
entity |
| Predicate | primaryTrafficRegion |
P182201
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Wikimedia servers, primaryTrafficRegion, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTrafficRegion Context triple: [Wikimedia servers, primaryTrafficRegion, global]
-
A.
primaryTransmitterRegion
Indicates the anatomical region that serves as the main source or origin of a transmitted signal or substance in the relationship.
-
B.
primary traffic
chosen
Indicates a relationship where a particular route, road, or data path serves as the main or most heavily used channel for traffic flow compared to alternatives.
-
C.
primaryLongHaulRegion
Indicates the main long-distance geographic region in which an entity primarily operates or is associated for long-haul activities.
-
D.
primaryHubRegion
Indicates that a given region serves as the main or central hub location for an entity or system.
-
E.
mainHostRegion
Indicates the primary geographic or network region in which a host or hosting environment is located or operates.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: April 28, 2026, 4:36 a.m.