Triple
T18021446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBN Butterfly parallel computer |
E431124
|
entity |
| Predicate | interconnectionTopology |
P33685
|
FINISHED |
| Object | butterfly 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: butterfly network | Statement: [BBN Butterfly parallel computer, interconnectionTopology, butterfly network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interconnectionTopology Context triple: [BBN Butterfly parallel computer, interconnectionTopology, butterfly network]
-
A.
interconnectionType
Indicates the specific kind or nature of relationship that links two or more entities together.
-
B.
interconnectionFrequency
Indicates how often two or more entities are connected or interact with each other over a given period.
-
C.
interconnectTechnology
Indicates a relationship where different technologies are linked or integrated so they can work together or share information.
-
D.
usesTopology
chosen
Indicates that one entity employs, is based on, or operates according to a particular topology defined or provided by another entity.
-
E.
networkModel
Indicates a relationship where an entity is represented or organized according to a specific network-based structure or framework.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c299c48190b0cceecf77cb6de9 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.