Triple
T146623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starlink satellite constellation |
E3343
|
entity |
| Predicate | networkArchitecture |
P4621
|
FINISHED |
| Object | mesh 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: mesh network | Statement: [Starlink satellite constellation, networkArchitecture, mesh network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkArchitecture Context triple: [Starlink satellite constellation, networkArchitecture, mesh network]
-
A.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
B.
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).
-
C.
architecture
chosen
Indicates the structural design or organizational framework that defines how components of a system or entity are arranged and interact.
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
originalNetwork
Indicates that one entity is the original or source network from which another network or derived entity is based or obtained.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256580c2c8190beecca60ca8595f3 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.