Triple
T187472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMP |
E4013
|
entity |
| Predicate | networkFunction |
P2637
|
FINISHED |
| Object | store-and-forward packet switching |
—
|
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 packet switching | Statement: [IMP, networkFunction, store-and-forward packet switching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkFunction Context triple: [IMP, networkFunction, store-and-forward packet switching]
-
A.
networkType
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.
network
chosen
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
C.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
D.
anodeFunction
Indicates that something serves as or relates to the functional role of an anode within an electrical or electrochemical system.
-
E.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594940e48190a3d8efbce46241c3 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25670feb081908e26a2543ebe7b3a |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.