Triple
T10158849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitnet Relay |
E233836
|
entity |
| Predicate | underlyingNetworkType |
P3937
|
FINISHED |
| Object | store-and-forward network |
—
|
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: store-and-forward network | Statement: [Bitnet Relay, underlyingNetworkType, store-and-forward network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingNetworkType Context triple: [Bitnet Relay, underlyingNetworkType, store-and-forward network]
-
A.
networkType
chosen
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
C.
basedOnNetwork
Indicates that something is determined, derived, or operates according to a particular network or network-related characteristics.
-
D.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
-
E.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec56d944819081bc6ea36c905ba2 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.