Triple
T17460006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsukuba International Congress Center |
E425126
|
entity |
| Predicate | hasNetworkConnection |
P32735
|
FINISHED |
| Object | internet access |
—
|
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: internet access | Statement: [Tsukuba International Congress Center, hasNetworkConnection, internet access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkConnection Context triple: [Tsukuba International Congress Center, hasNetworkConnection, internet access]
-
A.
isOnNetwork
Indicates that an entity is currently connected to, accessible through, or operating within a specified network.
-
B.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
C.
wifiAvailable
chosen
Indicates that a location, device, or context has access to a functioning Wi-Fi network.
-
D.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
-
E.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a3031c8190ab1dd0d41b002dd2 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.