Triple
T63905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPv4 |
E1269
|
entity |
| Predicate | widelyDeployedOn |
P2367
|
FINISHED |
| Object | global Internet |
—
|
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 Internet | Statement: [IPv4, widelyDeployedOn, global Internet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyDeployedOn Context triple: [IPv4, widelyDeployedOn, global Internet]
-
A.
usedOn
chosen
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
B.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
C.
operatingSystem
Indicates that one entity is the operating system running on, or used by, another entity.
-
D.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
E.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.