Triple
T9003445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messages |
E215087
|
entity |
| Predicate | usesNetworkForiMessage |
P55278
|
FINISHED |
| Object | Wi‑Fi |
—
|
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: Wi‑Fi | Statement: [Messages, usesNetworkForiMessage, Wi‑Fi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNetworkForiMessage Context triple: [Messages, usesNetworkForiMessage, Wi‑Fi]
-
A.
canUseNetworkType
chosen
Indicates that an entity is permitted or able to operate using a specified type of network.
-
B.
usesIP
Indicates that one entity makes use of, operates through, or is associated with a particular IP address.
-
C.
hasNetworkUS
Indicates that an entity possesses, operates, or is associated with a network located in or serving the United States.
-
D.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
E.
hasCellularComponent
Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6957bd5481908ce74f32f8d197de |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.